feature/LVA-6516: generate hardrestore image #107
Conversation
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
using crlf (win line endings) will produce weird errors when build into docker scripts
preparation for k8s deployment in local and connected contexts removes version line from docker-compose as it is deprecated updates the development readme regarding docker configuration
… with a default data dump
… confusing gh cr pages gh cr will tell users the sbom attestations can be used with docker
data and restoration logic will probably not change as often as app code; therefor manual building and release will suffice for now
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.
This PR adds a second github action workflow. The workflow builds a second container image which contains a utility to setup any postgres db with the example data dump. This is required in scenarios were a containerized, managed database is used in orchestrated dev environments and should be easily initialized with the data dump. In these situations a containerized tool which can be deployed to the same orchestrated environment is the simplest solution.
The new Dockerfile in the
sqlfolder creates such an utility image which contains only postgres client tooling and the data dump. The usage is explained in a new readme in the same folder.This workflow is only run when manually triggered, since it only needs updates when the data is updated.