From a REST API, we write to the database. We want to store who was the person that triggered this change. We have this information at the controller layer. The saving happens at the repository layer (We use spring boot, and have a service layer in between for business logic).
How can I stop leaking the auditing information to the business layer? If I pass the user from the controller to the repository, every method will have to take the user, either directly or wrapped in another object.
Is there a way to avoid this? Maybe specifically with Spring?