[x] I have checked for previous/existing GitHub issues
Description
Right now the only way to overwrite a policy assignment like in the Enable-DDoS-VNET example is by using a Management Group as the key for the policy_assignments_to_modify variable.
Working through using the ALZ provider most other targeting for changes like this are done at the Archetype scope. Having a way to scope would allow us to work at scale more in use cases where the Management Group and Archetype are not 1 to 1, and where the Archetype name is more predictable than the Management Group ID (This might be a edge case I'm happy to discuss over a call)
Check for previous/existing GitHub issues
Description
Right now the only way to overwrite a policy assignment like in the
Enable-DDoS-VNETexample is by using a Management Group as the key for thepolicy_assignments_to_modifyvariable. Working through using the ALZ provider most other targeting for changes like this are done at the Archetype scope. Having a way to scope would allow us to work at scale more in use cases where the Management Group and Archetype are not 1 to 1, and where the Archetype name is more predictable than the Management Group ID (This might be a edge case I'm happy to discuss over a call)