-
Notifications
You must be signed in to change notification settings - Fork 764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example Improvements related to issue #2135 (KeyVault secretsObject) #2139
Conversation
@alex-frankel thanks for the help getting this working!
realized I forgot the original issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this up
// https://github.com/Azure/bicep/issues/1754 | ||
|
||
// Also: | ||
// * KeyVaults secrets CANNOT BE EXPORTED into AMR/Bicep format. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you attempt export and secrets were not included?
// * KeyVaults secrets CANNOT BE EXPORTED into AMR/Bicep format. | ||
// * documentation: | ||
// https://docs.microsoft.com/en-us/azure/templates/microsoft.keyvault/vaults/secrets?tabs=json | ||
// * 201/key-vault-secret=create in pre-decompiled AMR format |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you mean ARM
not AMR
@@ -1,3 +1,16 @@ | |||
// | |||
// v0.3 Bicep Known issue & work-around related to "secretsObject" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's get rid of this comment assuming we uncomment the default secret object in the array parameter
@alex-frankel thanks for the help getting this working!
Contributing an example
dotnet test