[Enter feedback here]
In the outputs section it is stated
However for variables of type securestring the output will be masked and can't be use as an input for another deployment . Instead of passing secure information between deployments reference to that secret should be used
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@martgras Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.
@martgras - thanks for this suggestion. I have clarified how securestring behaves as an output type, and added a link to the Key Vault with templates article.
This is such a bad design ... the template outputs of type 'securestring' should be available but not recorded in log files.
I agree with @gigeld, what's the point of specifying an output if you can't use it? Why wouldn't it just return a value of type SecureString
and hide it in the deployment outputs view in the Azure Portal?
Most helpful comment
I agree with @gigeld, what's the point of specifying an output if you can't use it? Why wouldn't it just return a value of type
SecureString
and hide it in the deployment outputs view in the Azure Portal?