Minimum core CLI version support on the CLI extensions testing pipeline
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 60
Description
**Related command**
azdev test azext_connectedk8s.{function/command_to_test} --discover --live
**Is your feature request related to a problem? Please describe.**
The CLI extension testing pipeline runs all of the tests only for the latest CLI core version, not the minimum supported version, so for testing with minimum CLI core version , we have to do manual steps of uninstalling latest and installing older ones then run the tests locally. This becomes a manual testing rather than automated which may cause a miss on edge cases that may be added as part of the pipeline, basically not able to use the testing pipeline as a one stop solution to extension testing.
**Describe the solution you'd like**
Either the pipeline picks up the min CLI supported version from metadata file inside each extension repo code or the min CLI version can be one of the pipeline parameters and then the pipeline will test the extension by pulling that CLI version also along with the latest one for testing
**Describe alternatives you've considered**
The only alternative is to do manual testing locally with min CLI version and the testing pipeline can be used with latest CLI version which is neither a wholesome experience to the developer and nor the adoption of testing pipeline that easy when manual steps are required
**Additional context**
Link to the CLI testing pipeline - [https://dev.azure.com/azclitools/internal/_build?definitionId=131&_a=summary](url)
Contributor guide
Assessment
This issue has not been assessed yet.