chore: automatically set s3 scan status in dev #1050
Merged
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
Datadog ReportBranch report: ✅ 0 Failed, 827 Passed, 0 Skipped, 2m 40.19s Total Time |
Contributor
|
bugbot run |
kevinkim-ogp
approved these changes
Jun 12, 2025
Contributor
kevinkim-ogp
left a comment
kevinkim-ogp
left a comment
There was a problem hiding this comment.
lgtm, tested that it works! thanks for this 🙏
Contributor
Author
Merge activity
|
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.
Changes
Purely for dev ex, we automatically set GuardDutyStatus for postman attachments as NO_THREATS_FOUND in dev env since guard duty doesnt run in local minio server.