introduce pipeline.yaml file for CS #1016
Merged
Conversation
This file contains 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
geoberle
requested review from
bennerv,
janboll,
weinong,
whober0521,
tony-schndr,
jharrington22,
SudoBrendan,
UlrichSchlueter and
zgalor
as code owners
Signed-off-by: Gerd Oberlechner <[email protected]>
geoberle
force-pushed
the
cs-pipeline-file
branch
from
896393f to
3246099
Compare
tony-schndr
reviewed
Dec 20, 2024
cluster-service/deploy/helm/templates/azure-operators-managed-identities-config.configmap.yaml
Show resolved
Hide resolved
Signed-off-by: Gerd Oberlechner <[email protected]>
geoberle
force-pushed
the
cs-pipeline-file
branch
from
ff9a26d to
ccb77a0
Compare
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.
What this PR does
adopting pipeline.yaml required different handling for certain vars since functions like
ternaryare not available there.for the DB settings, i followed the same approach as for maestro, namely having dedicated preset value override files for the two scenarios.
additonally the operator configmap handling needed touching as well. since b64 encoding is not available the 6 operator role names are now provided via dedicated config.yaml vars. the rest of the information in the configmap is either the same in all environments (and can be defined directly in the configmap itself) or can be determined at runtime (e.g. the actual role resource IDs).
Jira:
Link to demo recording:
Special notes for your reviewer