Azure / Azure/azure-powershell

[Feature]: Support non-default runtimes for Automations

Open
#29,039 5 comments 2 reactions 0 assignees View on GitHub
act-codegen-extensibility-squad Automation customer-reported feature-request Service Attention Similar-Issue
Dominant language
C#
Stars
4.8k
Forks
4.3k
Avg merge
3d 14h
Merged PRs (30d)
54

Description

### Description of the new feature

Currently, the only way to upload PowerShell Modules or Python Packages to a non-default runtime is to use the portal. This process can be tedious and error-prone. This problem is exacerbated by the fact that the default runtimes are old, end-of-life versions of PowerShell and Python.

### Proposed implementation details (optional)

Accept a Runtime parameter to `New-AzAutomationModule` and `New-AzAutomationPython3Package`.

Contributor guide

Open the contributing guide

Research direction

Start by locating the implementations and tests for New-AzAutomationModule and New-AzAutomationPython3Package. Trace how their upload parameters are passed to Azure Automation, then add coverage for a non-default Runtime value. Done means both cmdlets accept and use Runtime while preserving default behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
cli, cloud
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.