[Container] Clarify PowerShell-safe env var passing for az container create#33457
Draft
Copilot wants to merge 3 commits into
Draft
[Container] Clarify PowerShell-safe env var passing for az container create#33457Copilot wants to merge 3 commits into
az container create#33457Copilot wants to merge 3 commits into
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
Collaborator
|
bug Fix |
Copilot
AI
changed the title
[WIP] Fix removal of special characters in environment variables via Azure CLI
[Container] Clarify PowerShell-safe env var passing for May 28, 2026
az container create
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related command
az container create --environment-variables --secure-environment-variablesDescription
PowerShell users reported that env var values containing
"and^were not reliably preserved when passed toaz container create. This PR tightens CLI guidance for that shell path and adds focused parser coverage for those characters.Help/UX updates
--environment-variablesand--secure-environment-variablesto explicitly call out PowerShell special-character handling and recommendazps.container createhelp example showing PowerShell usage via$env:variables.Targeted regression coverage
"and^are preserved.Testing Guide
Validate help/usage guidance in PowerShell for special-character values:
History Notes
[Container]
az container create: Clarify PowerShell-safe env var usage for values containing"and^This 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.