feat: Enable base constructs to automatically populate "created_by" and "last_updated_by" fields for relevant objects #1944
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Enable base constructs to automatically populate "created_by" and "last_updated_by" fields for relevant objects. We apply this to Tools, but this will set the foundation for future ORM refactors.
We also change it so we thread the entire actor (
User
) through the requests - this simplifies the API, and also allows us to do some simple access predicate checking where we confirm the actor of the request belongs to the organization the object (Tool, Agent) is associated with.Testing:
Ensured existing tests pass and added a new test case:
last_updated_by
field is updated butcreated_by
is not