use-protectedsettings-for-commandtoexecute-secrets -> protect-command… #5591
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.
use-protectedsettings-for-commandtoexecute-secrets -> protect-commandtoexecute-secrets
Fixes #5434
This is a breaking change for the bicep.config and #disable-next-line, but I think worth it (new rule, so not many people will be using it yet).
new aka.ms added: https://aka.ms/bicep/linter/protect-commandtoexecute-secrets -> https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/linter-rule-use-protectedsettings-for-commandtoexecute-secrets
I'm not changing the documentation URLs.
The old aka.ms doc link is still active so doc links for older bicep versions will continue to work: https://aka.ms/bicep/linter/use-protectedsettings-for-commandtoexecute-secrets