-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Generation of Code for new api 2024-09-01 for workloads #8177
base: main
Are you sure you want to change the base?
Conversation
❌Azure CLI Extensions Breaking Change Test
|
Hi @jaskisin, |
Thank you for your contribution! We will review the pull request and get back to you soon. |
CodeGen Tools Feedback CollectionThank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey |
|
…or virtual instance start/stop
Hello @kairu-ms, We are releasing the GA version of the CLI, shouldn't it be 2.0.0? also, we should be changing the option from preview to stable? as we are releasing the GA version of this:- |
…ing in workload modules
…nd update argument groups for clarity
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run |
Commenter does not have sufficient privileges for PR 8177 in repo Azure/azure-cli-extensions |
/azp run |
hi @jaskisin According to the version schema here: https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md#cli-extension-version-transition-table, cli extension modules can only increase major version number by at most one compared to the last stable version. Since there is no And since last version is And please remove the For more versioning schema info of cli extension repo, please refer to this doc: https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md |
removed the |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally? (pip install wheel==0.30.0
required)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.json
automatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json
.