[ContainerApp] Added support for Cloud Patching
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
- [x] Have you run
azdev style <YOUR_EXT>locally? (pip install azdevrequired) - [x] Have you run
python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required) - [x] My extension version conforms to the Extension version schema
For new extensions:
- [ ] My extension description/summary conforms to the Extension Summary Guidelines.
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.
⚠️Azure CLI Extensions Breaking Change Test
⚠️containerapp
rule cmd_name rule_message suggest_message ⚠️ 1006 - ParaAdd containerapp patch apply cmd containerapp patch applyadded parametercontainer_app_name⚠️ 1006 - ParaAdd containerapp patch apply cmd containerapp patch applyadded parameterpatch_name⚠️ 1011 - SubgroupAdd containerapp patch configure sub group containerapp patch configureadded⚠️ 1001 - CmdAdd containerapp patch delete cmd containerapp patch deleteadded⚠️ 1006 - ParaAdd containerapp patch list cmd containerapp patch listadded parametercontainer_app_name⚠️ 1001 - CmdAdd containerapp patch show cmd containerapp patch showadded
Hi @harryli0108, 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.
ContainerApp
:warning: Release Suggestions
Module: containerapp
- Update
VERSIONto1.0.0b1insrc/containerapp/setup.py
Notes
- Stable/preview tag is inherited from last release. If needed, please add
stable/previewlabel to modify it. - Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add
major/minor/patch/prelabel to adjust it. - For more info about extension versioning, please refer to Extension version schema
Please fix CI issues
Hi @harryli0108 Pleas follow the review process: Code Review Process When you send a new PR toAzure-CLI repo or Azure-CLI-Extensions repo, please make sure all checks in CI passed.
If the PR is to add new feature support, please get approval from your team who could be responsible for your business logic.