[AKS] Replace guardrails with safeguards#7260
Conversation
❌Azure CLI Extensions Breaking Change Test
|
|
Hi @NickKeller, |
|
AKS |
FumingZhang
left a comment
There was a problem hiding this comment.
Queued live test to validate the change.
- test_aks_create_with_safeguards
- test_aks_update_with_safeguards
Live test passed, and merge conflicts are resovled |
|
@FumingZhang is this good to be merged? |
src/aks-preview/HISTORY.rst
Outdated
| Pending | ||
| 2.0.0b1 | ||
| +++++++ | ||
| * Replace `guardrails` parameters with `safeguards`. |
There was a problem hiding this comment.
Since this change is a breaking change, it is better to specify "breaking change" in the history notes, so that users can be easily aware of that.
There was a problem hiding this comment.
@yanzhudd, does it matter even if the feature was never released?
There was a problem hiding this comment.
The major version was also increased too, users can see that
|
If there are no problems, can this please be merged? We are aiming for a kubecon eu release. |
|
[Release] Update index.json for extension [ aks-preview ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=134557&view=results |
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 azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)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.jsonautomatically.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.