Would be good if we could connect to our Stash server rather than having to use GitHub. Alternatively we have an on-prem TFS setup that we could also use. Data sovereignty issues prevent the use of GitHub/VSO at this time.28 votes
Thanks for your feedback on this! We are definitively interested in private/on-prem scenarios for source control.
As we start to do more development in this area, our team will follow up to get more details about your specific needs.
right now, while I can connect to github, the only thing I'm able to check-in or out are runbooks. This needs to be extended to both modules, configurations, and configuration data in order to provide functional DSC support.
Tracking configurations is critical to a proper dev-ops model, and in the current PowerShell implementation of DSC, that means BOTH configuration scripts as well as composite configurations stored as modules.
To take it further, company specific modules need to have the same ease of check-in/out, especially with the removal of versioning from the zip.21 votes
Thanks for this feedback. This is something that has been in our backlog, and having your input helps us to prioritize this.
You can currently write your own runbook to use to check in other artifacts as a workaround. You may want to take a look at http://blogs.technet.com/b/privatecloud/archive/2014/05/08/automation-mvp-spotlight-series-tfs-and-service-management-automation-better-together.aspx to see how this was done with TFS and convert to modules.
provide an option to allow users to unhide the runbooks that sync AA and Github to allow users to modify the process, with their custom process.
Use case would be adding an email notification or integrating with a ticketing system so their is a record of who preformed the sync and when in other system than the Azure Audit log.0 votes
Thanks for posting this! You can actually overwrite these scripts with your own content today just by importing a runbook with the same name as the script (just like global modules, these are global runbooks). So for example, you can name a script Sync-MicrosoftAzureAutomationAccountFromGithubV1 and your script will run when you click the “Sync” button.
In order for us to make these scripts public, we need to remove some proprietary code so this isn’t just as simple as releasing them. I’ll discuss with the team to see what we can do though.
- Don't see your idea?