Stop relying only on isHubCluster to enable the unsealJob #8
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.
Eventually we would like to drop isHubCluster as it is confusing and its
meaning does not always make sense (think of a standalone mcg setup.
I.e. one without ACM at all).
So let's enable the unsealJob either when isHubCluster is set to true
(in order to not break compatibility) or when in the application we
have the "hashicorp-vault" chart.
Tested on a standalone target for mcg and everything worked correctly.