Closed Joshua-Anderson closed 8 years ago
@arschles, @aledbf and @kmala are potential reviewers of this pull request based on my analysis of git blame
information. Thanks @Joshua-Anderson!
@@ master #407 diff @@
==========================================
Files 26 26
Lines 1098 1095 -3
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
- Hits 512 509 -3
Misses 555 555
Partials 31 31
Powered by Codecov. Last update 0690f89...d50cb23
We'd not have the push audit log anymore, not that it is exposed anywhere right now
Right now the push audit log isn't exposed anywhere. Is it worth exposing the push audit log and keeping the hook or getting rid of the audit log and the hook?
@gabrtv, @mboersma and @bacongobbler would have some context here
Overall I'm fine with removing the hook - A different audit log approach can also be introduced back in the future
Is it worth exposing the push audit log and keeping the hook or getting rid of the audit log and the hook?
what exactly are you referring to when you mean "the push audit log"? Haven't heard that terminology used before.
All this hook does is add the fields of the request to a table in the DB. None of our code actualy uses the table though.
This is the push model
ah I see. Yes, server side it's just validation. Nothing is done with the request.
@bacongobbler @mboersma I dont have much context with Push Hook can you guys take a quick look or we can punt this to the next sprint .
It was used for authorization, but the keys hooks is now used for both authentication and authorization.