-
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
Error setting the draft Automation Runbook, azurerm_automation_runbook fails with 404 Error - Unless Published version of runbook already exists #4403
Comments
i ran into this today with the both the regular and custom content examples listed in the documentation. |
I ran into this problem as well, using the |
I am running into the same problem
|
Yeah, for MR #3386 I've noticed that this started happening. This is due to the fact that MS basically removed the file the examples and tests were pointing to. If you are using the content parameter, a workaround is to point the url to any location as long as it exists. Even something like |
I just retried this and it seems I was wrong. I must've made a mistake when running apply. |
@erlacherl-city good to hear. The examples will hopefully be fixed once the MR is merged. |
I think the runbook_type enum is case specific. It needs to be "PowerShell" with a capital "S" |
Having the same issue here:
This is when creating a PowerShellWorkflow runbook |
I can confirm that setting the uri in the publish_conent_link block to something generic like https://google.com works. I had a fake URL that doesn't exist before. This may just need some error handling or maybe does not need to be required if setting the content for the script inline? I'm using heredoc content for the script content so I can fill in parameters from references to other resources in my file. Here is what my azurerm_automation_runbook resource looks like for reference: `resource "azurerm_automation_runbook" "start-bastion" { publish_content_link { content = <<EOC |
Just to muddle the water a bit; came across this issue the other day and pulled my hair out for a while. A generic URL such as Google will work for PowerShell runbooks, for PowerShell Workflows it won't; you need to provide a URI which will return text/plain (such as raw.githubusercontent.com). No idea why, however, it's the only thing that works for me for deploying a mixture of PoSH and PoSH WF - Using Google (or any other URI) worked fine when deploying just PoSH. |
Just to add what @mactator is telling, python scripts don't work either no matter what you set in the |
This has been released in version 2.9.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.9.0"
}
# ... other configuration ... |
This is not fixed in the version 2.9.0. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Terraform Configuration Files
Debug Output
Expected Behavior
Runbook should be created
Actual Behavior
Looking for creating runbook which doesn't exist
Steps to Reproduce
terraform apply
Terraform Version
Terraform v0.12.7
The text was updated successfully, but these errors were encountered: