Feat #1745: Support semver version ranges in helm_release version attribute - #1853
Open
dennismdejong wants to merge 1 commit into
Open
Feat #1745: Support semver version ranges in helm_release version attribute#1853dennismdejong wants to merge 1 commit into
dennismdejong wants to merge 1 commit into
Conversation
…rsion attribute
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR implements support for semver version ranges in the
versionattribute ofhelm_releaseresource andhelm_templatedata source.Changes
Updated schema descriptions - Updated the
versionattribute description in both the resource and data source to document that semver range syntax is supported (e.g.,^1.2.3,>= 1.0.0 < 2.0.0).Standard chart repositories - Version ranges already work natively with Helm's
ChartPathOptions.Versionfor non-OCI charts. No changes needed here beyond documentation.OCI chart version resolution - Added
resolveOCIVersionConstraint()function that resolves semver constraints for OCI charts by:registry.Client.Tags()ChartPathOptions.VersionThe OCI resolution is applied in both
chartPathOptions(resource) andchartPathOptionsModel(data source) when the repository is an OCI registry and the version is a non-empty constraint string.Fixes #1745