fix: issue at first run with lms and cms deployments#56
Merged
Conversation
MAAngamarca
approved these changes
Dec 18, 2023
Henrrypg
force-pushed
the
hpg/fix-initialization
branch
from
9ba2168 to
5f72edc
Compare
Ian2012
approved these changes
Dec 18, 2023
MoisesGSalas
approved these changes
Dec 18, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description
Currently, the first initialization of the "LMS" and "CMS" deployment modules fails when trying to look up tables before they were migrated in the jobs with ArgoCD Waves. This PR fixes the issue by placing these two deployments in the fourth wave after the jobs were run.