-
Notifications
You must be signed in to change notification settings - Fork 3.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
Import-AzureRmAutomationRunbook failing, when trying to update an existing Powershell Workflow runbook #5679
Comments
@vrdmr Hey Varad, would you mind taking a look at this issue? It seems there might already be a runbook with the same name, but a different type. Do you know if this is the case, and if so, is this operation allowed? |
The existing runbook, Type is returned as "runbookType": "Script", Script was a legacy value for PowerShellWorkflow. So seems like this is causing a BadRequest to be thrown on Re-PUT as PUT is sending runbookType: PowerShellWorkflow. This is a bug in service. As a workaround, Is it okay to delete and recreate the Runbook? Latest PUT will replace the legacy value Script to PowerShellWorkflow and there will be no badrequest reported. Get call will also return the runbookType:PowerShellWorkflow instead of legacy value. |
@safeermohammed Thanks for the response. We can delete and recreate the runbook in the Dev environment. But, we can't do that in the production environment. Could you please let me know when can we expect a fix for this issue? |
Out of curiosity, what happens to an existing runbook when the import of a new runbook failed? |
The existing runbook remains intact if the new runbook publish fails. |
assigning to @najams |
Fix was in b/e and it is deployed. Can you please try now? Please reopen the issue if it still repro's. |
Description
Import-AzureRmAutomationRunbook is returning a bad request, when we try to update an existing Powershell Workflow runbook.
Script/Steps for Reproduction
Module Version
5.4.1
Environment Data
Debug Output
The text was updated successfully, but these errors were encountered: