feat: support query parameters for list audit API #3970
Merged
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.
This pull request enhances the audit functionality by introducing support for query parameters in the
GetAudits
endpoint, improving the filtering and sorting of audit records, and updating the corresponding test cases. Below are the key changes:Enhancements to Audit Query Functionality:
GetAuditsQuery
struct inmanager/types/audit.go
to include new fields (ActorType
,ActorName
,EventType
,Operation
,State
,Path
, andStatusCode
) for filtering audit records. Each field has validation rules for allowed values and formats.GetAudits
method inmanager/service/audit.go
to apply filtering based on the new query parameters and to sort results bycreated_at
in descending order.Test Case Updates:
manager/handlers/audit_test.go
to verify theGetAudits
endpoint's behavior when query parameters are provided. This test ensures correct filtering, pagination, and response structure.Description
Related Issue
#3811
Motivation and Context
Screenshots (if appropriate)
Types of changes
Checklist