-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
resource: add MutateAndValidate endpoint #20311
Conversation
f577d8f
to
8527024
Compare
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.
Overall LGTM and I trust your judgment on the implementation as you have the greatest knowledge in this domain.
RE your comment about test improvements: I like what you've done here 👍
return false, status.Error(codes.InvalidArgument, err.Error()) | ||
} | ||
|
||
// ACL check comes before tenancy existence checks to not leak tenancy "existence". |
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.
👍
Co-authored-by: loshz <danbond@protonmail.com>
Co-authored-by: loshz <danbond@protonmail.com>
Description
See NET-6516 for context and acceptance criteria.
There is quite a bit of sharing between the
Write
endpoint and the newMutateAndValidate
endpoint sinceWrite
is a superset. I've DRY'ed things up a bit but didn't go off the rails (especially with the tests) to draw a balance with maintainability. e.g. The tests share test structs and test cases but not test methods. Open to better ways to structure this with maintainability in mind.Testing & Reproduction steps
Reviewers
PR Checklist