Decouple container image versions #1730
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
JaCoCo Test Coverage
|
yoomlam
added a commit
that referenced
this pull request
Jun 26, 2023
* GH Action: replace ENABLE_POSTGRES/CONSOLE with postgres/console_VER * add image-version.sh * create separate dbInit.imageTag * set default dbInit.imageTag
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 was the problem?
When deploying, we can only specify a single version for all container images.
Associated tickets or Slack threads:
How does this fix it?
Enable specifying versions of individual container images for deployment.
Versions specified in
scripts/image_versions.srcwill be used for deployment. If no version is specified thelatestis used.To be done in separate PR:
Update DeploymentGitHub Action workflowHow to test this PR
Run Update Deployment action and examine LHDI for expected result.