feat: use published container image #5
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
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.
Why
Automate container image build, publish, and security scanning in CI/CD to eliminate the need for developers to build images locally. Additionally, by automatically running yamory security scans when images are published, vulnerabilities can be detected early.
What
reusable-build-image.yaml: Add reusable Docker image build workflowreusable-yamory-scan.yaml: Add reusable yamory scan workflowpublish-image.yaml: Add workflow to build, publish, and scan images on push to main branchtest-build.yaml: Add workflow to test if build passes on PRsdocker-compose.yml: Change from local build to using published image from GHCRCONTRIBUTING.md: Add documentation for local development build instructionsHow to test
Checklist