Skip to content

Add support for development version overrides for components#1323

Draft
simu wants to merge 1 commit intomasterfrom
feat/test-version
Draft

Add support for development version overrides for components#1323
simu wants to merge 1 commit intomasterfrom
feat/test-version

Conversation

@simu
Copy link
Member

@simu simu commented Mar 20, 2026

This PR introduces optional field parameters.components.<component>.test_version.

Commodore will first try to checkout components.<component>.test_version for components who set the field, and fall back to field components.<component>.version if the version given in test_version is different to version and can't be checked out.

This feature might be useful on development or Lab clusters where many users test various component feature branches, and generally the absence of a configured version indicates that the feature branch was merged and the component's main development branch (usually master) should be used again.

Note that we probably should make this feature opt-in via a cluster fact or field in parameters.commodore.

TODO

  • Figure out if/how to feature gate this
  • Add test cases for the new functionality

Checklist

  • Keep pull requests small so they can be easily reviewed.
  • Update the documentation.
  • Update tests.
  • Categorize the PR by setting a good title and adding one of the labels:
    bug, enhancement, documentation, change, breaking, dependency, internal
    as they show up in the changelog

@simu simu added the enhancement New feature or request label Mar 20, 2026
@simu simu changed the title Add support for component version overrides which gracefully fall back to <component>.version Add support for development version overrides for components Mar 20, 2026
Commodore will first try to checkout `test_version` for components who
set the field, and fall back to field `version` if the version given in
`test_version` can't be checked out and isn't equal to `version`.

This feature might be useful on development or Lab clusters where many
users test various component feature branches, and generally the absence
of a configured version indicates that the feature branch was merged and
the component's main development branch (usually `master`) should be
used again.

Note that we probably should make this feature opt-in via a cluster
fact or field in `parameters.commodore`.
@simu simu force-pushed the feat/test-version branch from be36070 to a20fe4e Compare March 20, 2026 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant