Skip to content

Allow CLI to accept k8s version when creating clusters #228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

Dorthu
Copy link
Collaborator

@Dorthu Dorthu commented Mar 25, 2020

This is for linode/linode-cli#177

Right now, the "version" argument accepted when creating an LKE Cluster
translates in the CLI to --version, which the CLI interprets to mean
it should print its own version and exit.

For this reason, a new spec extension has been added,
x-linode-cli-name, which is allowed in schemas to define a new name
for the CLI argument for any POST/PUT attribute. To keep things
consistent between the API and CLI, this should be used only in extreme
circumstances (such as noted above).

This is for linode/linode-cli#177

Right now, the "version" argument accepted when creating an LKE Cluster
translates in the CLI to `--version`, which the CLI interprets to mean
it should print its own version and exit.

For this reason, a new spec extension has been added,
`x-linode-cli-name`, which is allowed in schemas to define a new name
for the CLI argument for any POST/PUT attribute.  To keep things
consistent between the API and CLI, this should be used only in extreme
circumstances (such as noted above).
@leslitagordita
Copy link
Contributor

@Dorthu when I test this locally (building the linode-cli from master), I receive an error:
linode-cli: error: unrecognized arguments: --kube-version 1.16

@Dorthu
Copy link
Collaborator Author

Dorthu commented Apr 6, 2020

Yeah, sorry, the associated CLI PR was closed because I'd already fixed this issue a different way 🙃 I'll close this as well.

@Dorthu Dorthu closed this Apr 6, 2020
LBGarber pushed a commit to LBGarber/linode-api-docs that referenced this pull request Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants