{containerapp} support connected env command group#6696
{containerapp} support connected env command group#6696zhoxing-ms merged 15 commits intoAzure:mainfrom
Conversation
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| containerapp connected-env | sub group containerapp connected-env added |
|
Hi @Greedygre, |
|
Hi @Greedygre, |
|
containerapp |
c1a211d to
f9ce817
Compare
|
Hi @zhoxing-ms @wangzelin007 |
src/containerapp/azext_containerapp/tests/latest/test_containerapp_preview_scenario.py
Show resolved
Hide resolved
Known issue, we have made the |
|
Hi @zhoxing-ms @yonzhan |
|
Hi @zhoxing-ms |
|
Suggest making the naming of folder for vendored sdk more readable |
Hi, this directory name is consisting with the |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az containerapp connected-env show/list/delete/create
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally?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.