-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
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
New resource: azurerm_automation update management configuration #2812
Comments
@franzoir Have you found a good way of automating the onboarding of the VMs to the automation account so the configuration can be applied? Everything I've seen says at least one VM needs to be onboarded manually first and then use a runbook to onboard the rest which is pretty horrible. Would love to automate this with Terraform! |
@OffColour I almost have a way that i'm happy with. Some tweaks still remain but I use Azure Policy to automatically onboard the VM to the correct Log Analytics workspace using tags to filter OS and WorkspaceName. Update management is then configured to automatically onboard VM linked to that workspace. Later on I'll also use tags to dynamically target VM update schedules. Last time i tested it didn't work well with pre/post scripts. |
@franzoir Just tested this out and worked perfectly with the automatic onboarding enabled. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
You said you are willing to share, can you paste your code somewhere? I hadn't considered using Policy. That seems like a great idea. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I just worked it out via [azurerm_template_deployment] after figuring out how to deal with the time offset. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
can anyone please specify the version of azurerm provider as this is not working for 2.20.0 TIA |
Since this is still a feature request and not an actually implemented thing.... This needs to be implemented first.... |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Did anyone get this to work with Azure Policies? I found this built-in policy didn't do what I expected. |
I've been meaning to try the new AzAPI terraform provider, where there is already an example for software update automation: https://github.com/Azure/terraform-provider-azapi/blob/main/examples/Microsoft.Automation/softwareUpdateConfigurations/main.tf Please let us know how it goes if you get a chance to test 🤞🏼 |
Given the expected resource has been supported as documented here, I'm closing this issue. Feel free to suggest re-activate if what is expected is still not implemented in this provider. |
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. |
Community Note
Description
We want to be able to deploy software update schedules via terraform.
We have configure a few standarized schedules that we will deploy to most of our customers, due to the amount of clicking in portal and lack of PS support for this resource, we would be very happy if this could be done from a terraform resource.
New or Affected Resource(s)
NEW RESOURCE
azurerm_automation_softwareUpdateConfigurations
Potential Terraform Configuration
Please refer to the following ARM template code for reference of configurable settings.
https://docs.microsoft.com/en-us/azure/templates/microsoft.automation/2017-05-15-preview/automationaccounts/softwareupdateconfigurations
References
The text was updated successfully, but these errors were encountered: