Add Support to Create ARM Template for policyDefinitions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, powershell
- Domain
- cloud
Research direction
The issue does not name a file, test, or entry point. Start by locating the policyDefinitions generation path and compare its current parameter-file output with the supplied JQ template; done means policyDefinitions are emitted as ARM templates with correctly handled policyRule expressions.
Written by the indexing model from the issue text.
Description
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": {}
}
- Dominant language
- PowerShell
- Stars
- 420
- Forks
- 174
- Avg merge
- 16d 18h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/AzOps
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
Similar issues
-
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Openbug ecr
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
hashicorp/go-azure-helpers#286 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#141 · 1 comment ·