az deployment * create --confirm-with-what-if cannot compare secureString values
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 60
Description
**Describe the bug**
When using any `az deployment * create` command with `--confirm-with-what-if`, if the template has any parameters with a type of `secureString` they will always be shown as being either modified or deleted and then created.
**To Reproduce**
Deploy any template with `az deployment * create --confirm-with-what-if` twice. As long as that template contains any parameters with a type of `secureString`, they will be shown as being either modified or deleted and then created.
**Expected behavior**
`--confirm-with-what-if` should be able to resolve `secureString` parameters and compare them to the existing parameters in the already-created resources.
For security reasons though, they should not be exposed in plain text if there is any type of difference between
**Environment summary**
Azure CLI v2.24.2 running in CentOS7 & Ubuntu 20.04LTS via WSL2, and in CentOS7 via Docker container on WSL2
OS: Windows 10 Enterprise 20H2
**Additional context**
N/A
Contributor guide
Assessment
This issue has not been assessed yet.