Description
We are replacing serviceName audit enum contract field with string, also removing the audit enums entirely
Notes are added to the endpoints that had used the enum, which suggests using the mapping endpoints first to get valid values
Change Category
Infrastructure
Informational
API
Change Context
There are instances of 'valid' values differing between pub-api-v2 enums and valid values used in the backend services call which may cause confusion.
Change Impact
No real impact; the same request bodies will work. A 400 error message will no longer be returned for an invalid enum value but a 400 error message can still be returned for other reasons. The 404 error message will now be returned consistently when an invalid value is provided.
Date of Change
Apr 13, 2023
Impacted APIs
/api/v2/audits/query/
/api/v2/audits/query/realtime
/api/v2/audits/query/realtime/trustor/{trustorOrgId}
References
[AUDIT-748]