As a Notify developer, I need to be able to debug our GitHub actions.
WHY are we building?
To prevent secrets from leaking we direct most GitHub action logs to /dev/null. Instead we could send them to Sentinel where they would be secure and we would be able to access them to debug problems that arise.
WHAT are we building?
Instead of directing logs to /dev/null, send them to Sentinel. Calvin and Pat (and probably others) know how to do this.
VALUE created by our solution
We can see why things fail and debug problems quickly.
Acceptance Criteria
[ ] Security is fine with us doing this
[ ] no logs sent to /dev/null, sent to Sentinel instead.
[ ] Notify devs have access and can find and examine the logs in Sentinel
QA Steps
[ ] Look at a specific action and find the logs for it
Description
As a Notify developer, I need to be able to debug our GitHub actions.
WHY are we building?
To prevent secrets from leaking we direct most GitHub action logs to /dev/null. Instead we could send them to Sentinel where they would be secure and we would be able to access them to debug problems that arise.
WHAT are we building?
Instead of directing logs to /dev/null, send them to Sentinel. Calvin and Pat (and probably others) know how to do this.
VALUE created by our solution
We can see why things fail and debug problems quickly.
Acceptance Criteria
QA Steps
Additional Information
SRE has already built a GitHub action to forward GitHub action data to Sentinel