We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the solution you'd like
At the moment, due to string escape requirement for policyRule, policyDefinitions Templates are generated as parameter file.
It would be great to have policyDefinitions generated as ARM template. Following JQ Template can help with that
{ "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "metadata": { "_generator": { "name": "AzOps" } }, "parameters": {}, "variables": {}, "resources": [ { "type": .Type, "name": .name, "apiVersion": "2021-06-01", "properties": { "description": .properties.description, "displayName": .properties.displayName, "metadata": { "version": .properties.metadata.version, "category": .properties.metadata.category }, "mode": .properties.mode, "parameters": .properties.parameters, "policyRule": .properties.policyRule | walk(if type == "string" and (.|startswith("[")) then "[" + sub("^\\["; "[") else . end), "policyType": .properties.policyType } } ], "outputs": {} }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the solution you'd like
At the moment, due to string escape requirement for policyRule, policyDefinitions Templates are generated as parameter file.
It would be great to have policyDefinitions generated as ARM template. Following JQ Template can help with that
The text was updated successfully, but these errors were encountered: