Azure / Azure/Azure-Landing-Zones
Use resourceSelector in built in policy
- Dominant language
- PowerShell
- Stars
- 97
- Forks
- 70
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 7
Description
### Community Note
- Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
### Versions
**terraform**: 1.6.6
**azure provider**: v3.88.0
**module**: 5.0.3
### Description
When trying to add a `resourceSelector` to an existing policy assignment, terraform does not detect the change.
#### Describe the bug
I added an archetype_config_overrides to override the Deny-Resource-Locations to allow me to deploy static web apps in another region than the on whitelisted.
```hcl
archetype_config_overrides = {
landing-zones = {
archetype_id = "es_landing_zones"
resourceSelector = {
Deny-Resource-Locations = {
name = "Allow static web app"
selector = {
in = []
kind = "resourceType"
not_in = [
"Microsoft.Web/staticSites",
]
}
}
}
}
}
```
#### Additional context
I can update the parameter easily but not the resource selector.
Contributor guide
Assessment
This issue has not been assessed yet.