Azure / Azure/ResourceModules

[Feature Request]: Enable utility version control in CI

Open
#2,660 1 comment 1 reaction 1 assignee Claimed by @AlexanderSehr View on GitHub
[cat] pipelines enhancement
Dominant language
PowerShell
Stars
737
Forks
436
Avg merge
10d 7h
Merged PRs (30d)
1

Description

### Description

The CARML CI currently does not provide out-of-the-gate capabilities to control which version of the uses tools (for example) are installed on the agents. As this can lead to issues (ref: #2641 #2659), we should implement a logic that optionally allows just that.

The idea could be 3 settings in the `settings.yml`:
- AzCLI version
- PowerShell version
- Bicep version

- and if they're set to '*' or 'latest' we could install latest.

The `Set-EnvironmentOnAgent` script already surfaces the used versions and in parts the code to install specific versions of e.g. Bicep.

In a first step we could concentrate on installing/updating - and in a second step on downgrading (if required)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.