-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
az containerapp up
: Fix InvalidResourceType error when cloud is not AzureCloud
#7551
az containerapp up
: Fix InvalidResourceType error when cloud is not AzureCloud
#7551
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
Hi @Greedygre, |
Hi @Greedygre, |
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
About Integration test failed, wait for pr: #7545 |
643e749
to
e313818
Compare
This comment was marked as resolved.
This comment was marked as resolved.
az containerapp up
: Fix InvalidResourceType error when cloud in AzureChinaCloud or AzureUSGovernmentaz containerapp up
: Fix InvalidResourceType error when cloud not in AzureCloud
az containerapp up
: Fix InvalidResourceType error when cloud not in AzureCloudaz containerapp up
: Fix InvalidResourceType error when cloud is not AzureCloud
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az cli fails because GET for "Connnected Environments" resource type fails
"Connnected Environments" resource type is not added to mooncake and fairfax
az containerapp connected-env
az containerapp up
Test with AzureCloud, we can see the
az containerapp connected-env
, with AzureChinaCloud, it cannot be found.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
.