Support for [Dynamic scoping for azurerm_automation_schedule ]

[DanLewis0]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction 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 and review the contribution guide to help.

Description

Hello,

As now Azure update Manager is in Global Availability and introduce a nice new feature "Dynamic scoping".
It would be nice to have "dynamic scoping" available in azurerm_automation_schedule also

Regards

New or Affected Resource(s)/Data Source(s)

azurerm_automation_schedule

Potential Terraform Configuration

No response

References

No response

[rcskosir]

@DanLewis0 Thank you for taking the time to open this feature request!

[gdinfragit]

I'd also like to see the Dynamic scoping added if possible. This will allow the use of tagging to dynamically add resources (e.g. VMs) into the Maintenance Schedule.

[jefutte]

Dynamic Scoping is part of Microsoft.Maintenance/configurationAssignments resource. It shouldn't be added to automation schedules config.

+1 for adding this to the azurerm provider. AzApi supports it: https://learn.microsoft.com/en-us/azure/templates/microsoft.maintenance/configurationassignments?pivots=deployment-language-terraform

[naikajah]

@jefutte were you able to use the az_api resource for adding Dynamic Scoping for Azure update manager configuration?

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.