-
Notifications
You must be signed in to change notification settings - Fork 4
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
Merge-up code to redact environment when logging Batch payloads #446
Conversation
Gtc-2194: Dont log Batch job envs (which include creds)
This doesn't seem to be working anymore - it is causing a permission error, even for admins with the gfw-pro app. So, I'm disabling this check temporarily until we figure out to how to make it work.
Disable wdpa_licensed_protected_area query permission check
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #446 +/- ##
==========================================
+ Coverage 80.28% 80.29% +0.01%
==========================================
Files 124 124
Lines 5503 5502 -1
==========================================
Hits 4418 4418
+ Misses 1085 1084 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Note that my PR #448 is in here, but I have already pushed it to origin/master, so it won't actually be part of this PR.
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.
Mega points for adding a test, @dmannarino! 💪
Pull request checklist
Please check if your PR fulfills the following requirements:
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this introduce a breaking change?
Other information