Describe the bug
Documenting this bug as a known issue with the newest release (10.2.0) of the PowerShell cmdlets. When attempting to use New-AzDeploymentStack cmdlets with a non-existing stack, a warning prompt will appear and incorrectly alert that a stack with that name already exists. In the opposite case, if a stack already exists and a New-AzDeployment stack cmdlet is used, a warning prompt will not appear (which is should) and the new stack will be upserted.
To Reproduce
Anytime using the New-Az*DeploymentStack cmdlets with the 10.2.0 version of Az PowerShell.
Navigating Around This Bug
Continue using the 10.1.0 version of Az Powershell. For the Deployment Stack cmdlets, the only feature update in 10.2.0 is better handling of tag upserts/deletion.
Use '-Force' flag to bypass warning prompts regardless.
Describe the bug Documenting this bug as a known issue with the newest release (10.2.0) of the PowerShell cmdlets. When attempting to use New-AzDeploymentStack cmdlets with a non-existing stack, a warning prompt will appear and incorrectly alert that a stack with that name already exists. In the opposite case, if a stack already exists and a New-AzDeployment stack cmdlet is used, a warning prompt will not appear (which is should) and the new stack will be upserted.
To Reproduce Anytime using the New-Az*DeploymentStack cmdlets with the 10.2.0 version of Az PowerShell.
Navigating Around This Bug