chore: secret scan in CodeBuild test #9657
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
As it turns out, our secret scan was flagging the 'account' part of the mapping generated for the AWS Deep Learning Containers image repositories. Turn them into 'repositoryAccount' instead to silence the scanner. Also, actually enable the scanner to run correctly for PR builds as well.
skinny85
force-pushed
the
fix/codebuild-gpu-images-secrets
branch
from
860cd58 to
f279e22
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
NetaNir
approved these changes
Aug 12, 2020
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
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.
As it turns out, our secret scan was flagging the 'account'
part of the mapping generated for the AWS Deep Learning Containers image repositories.
Turn them into 'repositoryAccount' instead to silence the scanner.
Also, actually enable the scanner to run correctly for PR builds as well.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license