Skip to content

Provide a reactive repository for audit events #32024

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.

Sign up for GitHub

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

Jump to bottom
Closed
vpavic opened this issue Aug 8, 2022 · 1 comment
Closed

Provide a reactive repository for audit events #32024

vpavic opened this issue Aug 8, 2022 · 1 comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement

Comments

@vpavic
Copy link
Contributor

vpavic commented Aug 8, 2022

With its current API where all operations are of blocking nature, AuditEventRepository cannot be properly implemented using a non-blocking data store and is therefore not really suitable for use on a reactive runtime.
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 8, 2022
@vpavic vpavic mentioned this issue Sep 5, 2022
Closed
@wilkinsona wilkinsona added the for: team-meeting An issue we'd like to discuss as a team to make progress label Sep 27, 2022
@wilkinsona wilkinsona added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged for: team-meeting An issue we'd like to discuss as a team to make progress labels Oct 13, 2022
@wilkinsona wilkinsona added this to the 3.x milestone Oct 13, 2022
@wilkinsona wilkinsona changed the title AuditEventRepository is not suitable for reactive Provide a reactive repository for audit events Oct 13, 2022
@wilkinsona
Copy link
Member

We’re cleaning out the issue tracker and closing issues that we’ve not seen much demand to fix. Feel free to comment with additional justifications if you feel that this one should not have been closed.

@wilkinsona wilkinsona closed this as not planned Won't fix, can't repro, duplicate, stale Apr 25, 2025
@wilkinsona wilkinsona removed this from the 3.x milestone Apr 25, 2025
@wilkinsona wilkinsona added the status: declined A suggestion or change that we don't feel we should currently apply label Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wilkinsona @vpavic @spring-projects-issues