-
Notifications
You must be signed in to change notification settings - Fork 2
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
[DSEC-907] Notify AppSec team when Trivy action fails #337
Conversation
zbedo
commented
Jul 25, 2024
•
edited
Loading
edited
- Submitter: Include the JIRA issue number in the PR description
- Submitter: Make sure Swagger is updated if API changes
- Submitter: If updating admin endpoints, also update firecloud-admin-cli
- Submitter: Check documentation and code comments. Add explanatory PR comments if helpful.
- Submitter: JIRA ticket checks:
- Acceptance criteria exists and is met
- Note any changes to implementation from the description
- To Demo flag is set
- Release Summary is filled out, if applicable
- Add notes on how to QA
- Submitter: Update RC_XXX release ticket with any config or environment changes necessary
- Submitter: Update FISMA documentation if changes to:
- Authentication
- Authorization
- Encryption
- Audit trails
- Submitter: If you're adding new libraries, sign us up to security updates for them
- Tell the tech lead (TL) that the PR exists if they wants to look at it
- Anoint a lead reviewer (LR). Assign PR to LR
- Review cycle:
- LR reviews
- Rest of team may comment on PR at will
- LR assigns to submitter for feedback fixes
- Submitter rebases to develop again if necessary
- Submitter makes further commits. DO NOT SQUASH
- Submitter updates documentation as needed
- Submitter reassigns to LR for further feedback
- TL sign off
- LR sign off
- Product Owner sign off
- Assign to submitter to finalize
- Submitter: Verify all tests go green, including CI tests
- Submitter: Squash commits and merge to develop
- Submitter: Delete branch after merge
- Submitter: Test this change works on dev environment after deployment. YOU own getting it fixed if dev isn't working for ANY reason!
- Submitter: Verify swagger UI on dev environment still works after deployment
- Submitter: Inform other teams of any API changes via Slack and/or email
- Submitter: Mark JIRA issue as resolved once this checklist is completed
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.
Seems great to me once @zbedo confirms the SLACK_WEBHOOK_URL
value is set 👍
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.
Agreed with Adam, change looks good, but just need to make sure the secret is in place
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.
LGTM with one extremely minor suggestion.
Co-authored-by: Adam Nichols <aednichols@gmail.com>