Continuous Deployment of runbooks
I have runbooks that are stored in source control which then get deployed to Azure Automation. The process of deploying them is rather cumbersome (basically a bunch of hand crafted Powershell scripts that call the Azure Automation cmdlets). It seems to me that there are going to be lots of people crafting the same kind of scripts - that's a lot of wheel-reinvention going on.
I'd like to see some features introduced that support quick and easy Continuous Deployment of runbooks (i.e. I check them into source control and they automatically get deployed to Azure Automation).
-Support Continuous Deployment to an Azure Automation account from Dropbox & Visual Studio Online (i.e. the same which are supported for Azure websites)
-Package up a bunch of runbooks into a single deployable, portable, entity. In the SQL Server database world we have dacpacs for doing this, I'd like something analogous for Azure Automation runbooks. Lets call such a thing a "runpac" for now.
-"runpacs" should be supported on SMA too.
-Ability to "publish" a "runpac" into an Azure Automation account. The publish operation should be idempotent (i.e. if a runbook of the same name already exists, it gets replaced, otherwise it simply gets created). The publishing operation should report whether runbooks are created or replaced. There should be the ability to specify whether the runbooks therein are created as draft or published. etc... lots of possibilities if you were to implement this notion of "runpacs".
Thank you for the feedback. The product team has noted this suggestion and will consider it if resourcing allows.
joe brockhaus (rax) commented
Any update on this?
joe brockhaus commented
I've created a PowerShell Module that can be easily imported into your Automation Account to Sync runbooks from VSO-Git.
This picks up where the incomplete Sync-VsoGitRunbook left off, and doesn't require manual dependency management nor obtuse folder structures.
The GitHub repo contains sample runbooks and instructions for how to configure VSO Service Hooks & create the Runbook WebHook to receive the VSO events.
Jamie Thomson commented
After discussion with Joe Levy (http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/967113a6-bc4c-460a-a3b1-6558d4080d2a/continuous-deployment-of-runbooks?forum=azureautomation) I conccur with his thoughts that ARM templates would probably be more suitable in this scenario.