microsoft / microsoft/azure-linux-dev-tools

[Feature]: Allow overriding project.default-distro on the azldev command line

Open
#226 0 comments 0 reactions 0 assignees View on GitHub
enhancement priority: low
Dominant language
Go
Stars
18
Forks
27
Avg merge
4d 33m
Merged PRs (30d)
24

Description

**Is your feature request related to a problem? Please describe.**
`project.default-distro` is consumed by several commands as the implicit target when no explicit distro is specified.
For example, in `azldev repo query --version `, `--version` requires `project.default-distro.name` to be set in project config.

Today the only way to retarget is to mutate `azldev.toml`, which is awkward when:
- experimenting with a different distro version locally (e.g., azurelinux 4.0 vs 4.1),
- running ad-hoc one-off commands against a different distro,
- driving azldev from CI/scripts that shouldn't have to template the TOML.

**Describe the solution you'd like**
Add global CLI flags that take precedence over `project.default-distro`:
```
--default-distro # override project.default-distro.name
--default-distro-version # override project.default-distro.version
```
Or
```
--default-distro name=azurelinux,version=4.0
```

Contributor guide

Open the contributing guide

Research direction

Start with the azldev global CLI parsing and trace how project.default-distro is consumed by azldev repo query --version. Use azldev.toml to verify the existing configuration shape; done means the requested command-line override takes precedence without requiring TOML changes, including separate name and version flags or the combined form.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, devtools
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.