Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
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>
|
There was a problem hiding this comment.
Pull Request Overview
This PR fixes issue #32107 where az containerapp registry show command throws a NoneType error when the --server parameter specifies a non-existent registry server. The fix adds proper validation to handle empty or null registry configurations.
Key Changes:
- Adds validation to check for null or empty registry definitions before iterating
- Adds test coverage to verify the fix handles non-existent registry servers correctly
- Removes duplicate
@live_only()decorator from existing test
Reviewed Changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| custom.py | Adds null/empty check for registry definitions to prevent NoneType errors |
| test_containerapp_scenario.py | Adds test case for non-existent registry server and cleans up duplicate decorator |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
az containerapp registry show: Fix NoneType error when --server specifies a non-existent registry serveraz containerapp registry show: Fix NoneType error when container app doesn't have registry server
az containerapp registry show: Fix NoneType error when container app doesn't have registry serveraz containerapp registry show: Fix NoneType error when container app doesn't have any registry server
|
@microsoft-github-policy-service rerun |
…NoneType error when container app doesn't have any registry server (Azure#32270)
Fix issue: #32107
Related command
az containerapp registry show
Description
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.