Support p2p traffic encryption.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az containerapp env create/update
General Guidelines
- [ ] Have you run
azdev style <YOUR_EXT>locally? (pip install azdevrequired) - [ ] Have you run
python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required) - [ ] 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 env create cmd containerapp env createadded parameterp2p_encryption_enabled⚠️ 1006 - ParaAdd containerapp env update cmd containerapp env updateadded parameterp2p_encryption_enabled
Hi @LGDoor, 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.
: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
pending on 2024-02-02-preview
@Greedygre @Juliehzl plz review
please get approval from your team who could be responsible for your business logic.
The CI integration Failed is due to the azure-cli has upgraded api-version to 2024-03-01, I will update the recording files soon.
@zhenqxuMSFT plz help review
The CI integration Failed is due to the azure-cli has upgraded api-version to 2024-03-01, I will update the recording files soon.
The PR has been merged, please rebase the main.
Recommend title:
[Container app] az containerapp env create/update: Support peer-to-peer traffic encryption with --enable-peer-to-peer-encryption