Azure / Azure/azure-powershell
[Feature]: Add support for Runtime Environments to Az.Automation
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 4.3k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 51
Description
### Description of the new feature
The Az.Automation module doesn't support the use Automation Runtime Environments. This leaves only the Azure Portal and the REST API as the only method for automating the use of Runtime Environments. In particular the New-AzAutomationModule, Import-AzAutomationRunbook and associated Cmdlets do not allow you to target a Runtime Environment when importing runbooks and modules.
I note that Azure CLI has very limited support for Runtime Environments but this is incomplete, doesn't support importing runbooks and modules and a lot of commands for automation appear to still be experimental.
### Proposed implementation details (optional)
Add a -RuntypeEnvironment parameter to relevant commands so that it is possible to automate the use of Runtime Environments via PowerShell.
Contributor guide
Research direction
Start by locating New-AzAutomationModule, Import-AzAutomationRunbook, and the associated cmdlets, then read how their existing parameters are defined. Compare the requested Runtime Environment targeting with the issue's REST API and Azure CLI context; done means relevant runbook and module imports can target a Runtime Environment through the requested parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, powershell
- Domain
- cloud, devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100