-
Notifications
You must be signed in to change notification settings - Fork 116
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
chore: use internal build-scan-push for security scans #4044
base: develop
Are you sure you want to change the base?
Conversation
Allure Test reports for this run are available at: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4044 +/- ##
========================================
Coverage 91.00% 91.00%
========================================
Files 629 629
Lines 32824 32827 +3
Branches 7788 7788
========================================
+ Hits 29871 29874 +3
Misses 2734 2734
Partials 219 219 ☔ View full report in Codecov by Sentry. |
@@ -36,6 +36,10 @@ on: | |||
DOCKERHUB_PROD_TOKEN: | |||
required: true | |||
|
|||
permissions: |
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.
what is the use of these?
Allure Test reports for this run are available at: |
Allure Test reports for this run are available at: |
|
Allure Test reports for this run are available at: |
What are the changes introduced in this PR?
We are moving to a custom
docker-build-scan-push
workflow which takes care of scaning the repo for secrets using trufflehog before building the image.What is the related Linear task?
Resolves INT-3167
Please explain the objectives of your changes below
Improving security
Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?
No
Any new dependencies introduced with this change?
rudderlabs/docker-scan-build-push
Any new generic utility introduced or modified. Please explain the changes.
No
Any technical or performance related pointers to consider with the change?
No
@coderabbitai review
Developer checklist
My code follows the style guidelines of this project
No breaking changes are being introduced.
All related docs linked with the PR?
All changes manually tested?
Any documentation changes needed with this change?
Is the PR limited to 10 file changes?
Is the PR limited to one linear task?
Are relevant unit and component test-cases added in new readability format?
Reviewer checklist
Is the type of change in the PR title appropriate as per the changes?
Verified that there are no credentials or confidential data exposed with the changes.