[patch] Move MAS instance Mongo data wipe job to sync-jobs application #1144
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
added 3 commits
July 25, 2024 15:53
(since the data wipe logic has been moved into the sync-jobs application, we need this flag to be available there)
tomklapiscak
requested review from
durera,
andrercm,
sanjayprab,
terenceq,
whitfiea,
alequint and
leo-miran
as code owners
3 tasks
terenceq
approved these changes
Jul 31, 2024
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.
https://jsw.ibm.com/browse/MASCORE-3100
Supporting changes for PR ibm-mas/gitops#176.
Was necessary to move the
MAS_WIPE_MONGO_DATAflag toibm-mas-instance-base.yamlso it can be supplied to the sync-jobs application.Associated saas-tekton pipeline updates are here: https://github.ibm.com/maximoappsuite/saas-tekton/pull/54
Testing
Updated Pipeline/Tasks/Functions executed successfully:
mas_wipe_mongo_dataflag included inibm-mas-instance-base.yamlas expected: