We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The shp CLI currently uses the v1alpha1 API for all its calls. In order to stop serving the v1alpha1 API, all clients must migrate to the v1beta1 API.
shp
v1alpha1
v1beta1
Use the v1beta1 API for all calls. This may require us to deprecate CLI commands or flags/options that rely exclusively on the v1alpha1 API.
Keep using the v1alpha1 API - this isn't a good long term option. It also blocks us from adopting new features that land in the v1beta1 API only.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there an existing feature request for this?
Is your feature request related to a problem or use-case? Please describe.
The
shp
CLI currently uses thev1alpha1
API for all its calls. In order to stop serving thev1alpha1
API, all clients must migrate to thev1beta1
API.Describe the solution that you would like.
Use the
v1beta1
API for all calls. This may require us to deprecate CLI commands or flags/options that rely exclusively on thev1alpha1
API.Describe alternatives you have considered.
Keep using the
v1alpha1
API - this isn't a good long term option. It also blocks us from adopting new features that land in thev1beta1
API only.Anything else?
No response
The text was updated successfully, but these errors were encountered: