kubernetes-client/gen/openapi/python.sh - 'no such file or directory' exec error
marie-yau opened this issue · comments
An error occurred when executing kubernetes-client/gen/openapi/python.sh
Following the instructions under the “Generating a client”
( https://github.com/kubernetes-client/gen ):
${CLIENT_LANGUAGE}.sh OUTPUT_DIR SETTING_FILE
Below is an example run:
/root/kubernetes/gen/openapi/python.sh /root/output_client/kubernetes /root/kubernetes/python/settings
The /root/kubernetes/python/settings files is as follows:
export KUBERNETES_BRANCH="master"
export CLIENT_VERSION="8.0.0b1"
export PACKAGE_NAME="kubernetes"
The stdout from the above run is shown below, revealing an execution find error in the last line:
...
---Done.
--- Patching generated code ...
find: '/root/output_client/kubernetes/client/': No such file or directory
...
I will submitt a PR to the kubernetes-client/gen repo to remedy the execution error above.
The fix involved modifying: /root/kubernetes/gen/openapi/python.sh
Your settings file should have
export PACKAGE_NAME="client"
, because the generated code lands as the sub-directory /client
within the package: https://github.com/kubernetes-client/python/tree/master/kubernetes/client
BTW, if you need to regenerate client you can use the script https://github.com/kubernetes-client/python/blob/master/scripts/update-client.sh which does the job.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen
.
Mark the issue as fresh with/remove-lifecycle rotten
.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.