[ci_gen_kustomize_values] Skip startingCSV when deployment version is "latest" #3657
+6
−6
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.
This is a followup of #3653
Add "latest" to the exclusion list in OLM values templates to prevent generating an invalid startingCSV field. When
cifmw_ci_gen_kustomize_values_deployment_versionis set to "latest", the openstack-operator-version field is now skipped, allowing OLM to automatically select the latest CSV from the channel.This fixes ConstraintsNotSatisfiable errors caused by OLM trying to find a CSV literally named "latest" which doesn't exist.