-
Notifications
You must be signed in to change notification settings - Fork 4
scan docker images #201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
scan docker images #201
Conversation
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR implements Docker image scanning functionality by adding Docker build and push targets to the Makefile and introducing a new GitHub Actions workflow for pre-merge scanning of Docker images.
- Adds standardized Docker build/push targets for all services in the Makefile
- Introduces version suffix support for image retagging in CI environments
- Adds pre-merge scanning workflow that builds and scans Docker images for security vulnerabilities
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
Makefile | Adds Docker build/push targets with service matrix support and version suffix retagging |
.github/workflows/lint-test-build-publish.yml | Adds pre-merge workflow for building and scanning Docker images across all services |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Description
Please include a summary of the changes and the related issue. List any dependencies that are required for this change.
Fixes # (issue)
Any Newly Introduced Dependencies
Please describe any newly introduced 3rd party dependencies in this change. List their name, license information and how they are used in the project.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: