terraform-provider-azurerm
terraform-provider-azurerm copied to clipboard
Support for Automation Hybrid Runbook Worker Group
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
Description
This is a request for a new resource in automation category for Hybrid Runbook Worker Group.
New or Affected Resource(s)
- azurerm_automation_hybrid_runbook_worker_group
Potential Terraform Configuration
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.
References
- https://github.com/Azure/azure-sdk-for-go/blob/main/services/automation/mgmt/2019-06-01/automation/hybridrunbookworkergroup.go
without the ability of having hybrid worker available is indeed pretty much useless.
This would be very helpful!
Hi Team, Can please let me know when this new resource will be available. These are very much required for Azure Automation Accounts to connect Azure Services like Key Vault and Storage Account which are configured via PrivateEndPoints. Looking forward for this new resource "azurerm_automation_hybrid_runbook_worker_group" . Thanks in advance
Agreed - I can create the automation account, create the runbook, create the schedule, and even create a job schedule pointing at an existing hybrid worker group, but without this resource, I'd always have to break this into two deployments to allow manual provisioning, put a local-exec block in, or run an ARM template before I can close the loop.
@WaitingForGuacamole perhaps consider use of the azapi_resource that can handle bicep compatible templates - I've managed to deploy a hybrid worker group using it, example below:
resource "azapi_resource" "hybrids_group_1" {
type = "Microsoft.Automation/automationAccounts/hybridRunbookWorkerGroups@2022-02-22"
name = "hwg-${azurerm_automation_account.hybrids.name}-001"
parent_id = azurerm_automation_account.hybrids.id
body = jsonencode({
properties = {
credential = {
name = azurerm_automation_credential.domain_service_account.name
}
}
})
}
There are Terraform examples in the documentation. Its quite useful for stuff on the fringes, like this.
This functionality has been released in v3.21.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.
For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!
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.