Features mismatch for deployment stacks #32680
Description
Describe the bug
The --validation-level argument in deployment create commands is not reflected when deploying through the deployment stack commands, and there does not appear an alternative argument that matches this functionality.
I have encountered this issue when deploying a 'deployment script', which as part of the prerequisites creates a policy exemption to work-around incompatibilities of deployment scripts and WAF environments. If validation is performed as part of the deployment command, it is not aware of changes contained within that alter the validation process and so fail. Leveraging the validation-level argument enables deployment to work as expected.
When transitioning to a deployment stack to ensure resource integrity and removal on completion, the same logic cannot be applied as the deployment stack commands are missing the validation-level argument.
Related command
az stack mg create
az stack sub create
az stack group create
Errors
unrecognized arguments: --validation-level Template
Issue script & Debug output
az stack sub create -o none -l uksouth --aou deleteAll --dm none --yes -p whatever.bicepparm --validation-level Templatecli.azure.cli.core.azclierror: unrecognized arguments: --validation-level Template
az_command_data_logger: unrecognized arguments: --validation-level Template
Expected behavior
I expect that when deploying a subscription or resource group via a deployment stack for the behaviour to be consistent to ensure that ARM templates/bicep files are idempotent and work in the same way regardless of the deployment management approach.
Environment Summary
{
"azure-cli": "2.81.0",
"azure-cli-core": "2.81.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"application-insights": "1.2.3",
"azure-devops": "1.0.2",
"containerapp": "1.2.0b1",
"logic": "1.1.0"
}
}Additional context
No response