Ensure helm release build consistently handles deployOLM toggle #2066
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.
Summary: Ensure helm release build consistently handles deployOLM toggle
Splitting the csv-deleter Job into its own file in #2063 introduced a bug where the
px-operator
namespace becomes stuck onhelm uninstall
again. This is because helm'sdeployOLM
configuration key is patched for the 00_olm.yaml file during the release build. When I initially tested in #2059, the csv-deleter Job existed in the file and received this special treatment, but after #2063 it no longer did.In order to address this, this change introduces a Go template comment placeholder that
sed
will look to make it clear that helm operates with a different conditional check. It also runs this sed command across all template files and not just the00_olm.yaml
file. This comment will be stripped out during thepx
cli's yaml templating and will leave it'sdeployOLM
conditional check intact.Relevant Issues: #1917
Type of change: /kind bug
Test Plan: Ran the sed command and verified that it works