Open ajaykn opened 2 days ago
Hi @ajaykn, Please write the description of changes which can be perceived by customers into HISTORY.rst. If you want to release a new extension version, please update the version in setup.py as well.
Thank you for your contribution! We will review the pull request and get back to you soon.
Thank 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
For more info about extension versioning, please refer to Extension version schema
❌Azure CLI Extensions Breaking Change Test
❌mdp
❌ 1007 - ParaRemove mdp pool create cmd
mdp pool create
removed parameterprovisioning_state
please add back parameterprovisioning_state
for cmdmdp pool create
This is fine, since it was a bug in older version. we dont support this parameter in creation flow.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
Command:
az mdp
We have latest version of mdp "Microsoft.DevOpsInfrastructure" Resource provider api to 2024-04-04-preview
https://github.com/Azure/azure-rest-api-specs/tree/main/specification/devopsinfrastructure/resource-manager/Microsoft.DevOpsInfrastructure/preview/2024-04-04-preview
As part of this PR, we upgrade the commands to latest version and support the new commands New commands are
Related PR in aaz models: https://github.com/Azure/aaz/pull/511
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
.