It would be nice to have the option to migrate a runbook to another Automation Account. With a user action, on whether or not assets and stuff, associated to the runbook, should be moved too.
I see it useful in a Test / Prod environment. We want multiple users to be able to develop runbooks, but only in a controlled environment. And then move it to our production Automation Account when done.21 votes
Thanks for posting this suggestion. We do have integration with source control which would easily enable you to sync your runbooks from a dev to prod account easily. https://azure.microsoft.com/en-us/blog/azure-automation-source-control-13/
Are you asking to be able to pick a runbook and supporting assets and then move them to another account? Would being able to group them together and export them as an ARM template work as a potential solution or is your preference to have a tool in the UX to do this?
It would be awesome if you would add Azure Automation node library to your azure-sdk-for-node.
Really looking forward for this!13 votes
Thanks for sharing this feedback. As Joe mentioned on GitHub, the team is looking at this.
- Don't see your idea?