How can we improve Azure Automation service?

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).

Some ideas:
-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".

36 votes
Vote
Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
You have left! (?) (thinking…)
Jamie Thomson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3 comments

Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base