-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[Container app] az containerapp env create: Add parameter --infrastructure-resource-group to support specifying name for resource group that will contain infrastructure resources
#32457
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
base: dev
Are you sure you want to change the base?
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @Greedygre, |
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| containerapp env create | cmd containerapp env create added parameter infrastructure_resource_group |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
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.
Pull request overview
This PR adds support for the --infrastructure-resource-group parameter to the az containerapp env create command, migrating this functionality from the containerapp extension to the Core CLI. The parameter allows users to specify a custom resource group name for infrastructure resources when creating a container app environment.
- Added parameter definition with
-ishort option for infrastructure resource group - Implemented validation requiring both subnet resource ID and workload profiles to be enabled
- Added property assignment logic in the environment decorator
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| _params.py | Adds the --infrastructure-resource-group/-i parameter definition with help text |
| custom.py | Adds the infrastructure_resource_group parameter to the create_managed_environment function signature |
| containerapp_env_decorator.py | Implements getter, validation logic, and property assignment for the infrastructure resource group |
| test_containerapp_env_commands.py | Adds E2E test for the infrastructure resource group feature |
| custom_preparers.py | Introduces SubnetPreparer for test setup |
| common.py | Adds STAGE_LOCATION constant for test configuration |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
src/azure-cli/azure/cli/command_modules/containerapp/tests/latest/custom_preparers.py
Show resolved
Hide resolved
|
Please fix CI issues |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
az containerapp env create: Support --infrastructure-resource-groupaz containerapp env create: Add parameter --infrastructure-resource-group to support specifying name for resource group that will contain infrastructure resources
az containerapp env create: Add parameter --infrastructure-resource-group to support specifying name for resource group that will contain infrastructure resourcesaz containerapp env create: Add parameter --infrastructure-resource-group to support specifying name for resource group that will contain infrastructure resources
Move property
--infrastructure-resource-groupin containerapp extension to Core CLIRelated command
az containerapp env createDescription
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.