Add tagging for variables/credentials and connection for central management in multi-tier SMA environment
This is a scenario that came up recently thinking about multi-tier SMA environments. Where one have different AD's isolated from each other, but wanting a central master SMA orchestrator.
As for Runbooks where one can use tags as a means to target and distribute the code to different SMA installations downstream. This would also be nice to have for assets types, as this would allow a similar distribution scenario. Enabling having a (HA) central SMA installation where all assets are maintained.
Even better would be a scenario where one could figure out how to allow for assets with the same name, but categorized into different groups. Like Test, QA, Prod. This would allow for reuse of assets in code without needing extra logic to differentiate the current execution SMA environment. I.e running the same code in different environments but with assets that have environment different content (though accessed through the same name in the code).
This would give a huge reuse boost, and lessen the maintenance burden.
Thanks for this suggestion!
Would creating accounts that can group runbooks and assets solve this? If you look at Azure Automation, we allow users to create accounts which should enable what you are talking about.
I guess this could work. Would be nice in a scenario like that to be able to share some runbooks and assets between accounts, and keep others strictly isolated pr account. Content of one account could then be targeted for sync with a downstream headless SMA client.
If one could set up multiple accounts on the same SMA install, and access them through the WAP GUI would be a good compromise i guess.