feat(phoenix/tenant-portal#413): record the request's azp on the revision #245
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
phoenix-oss/quarkus-commons!245
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/revision-azp"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Records the OIDC authorized party (azp) of the request that produced a revision, next to the actor — the growing set of portal API clients becomes observable per revision.
Refs phoenix/tenant-portal#413
Changes
TracingConstants.AZPMDC key (azp) andTracingService.getAzp()reading the MDC. The key follows the Temporal precedent: the library reads it but does not set it — the consuming application owns recording it per request (e.g. an OIDC filter).Revision.azpcolumn (revinfo),RevisionContextProvider.getAzp(), theDefaultRevisionContextProviderimplementation and theAuditRevisionListenerwiring — the same pattern as every other context field.V4__add_revision_azp.sqland updated tests for the new getter and the revinfo column.Verification
./mvnw -pl quarkus-tracing-service,quarkus-audit-tools -am verify— BUILD SUCCESS; JaCoCo module checks met (100% audit-tools, 95% tracing-service).Shipping
Feature work ships on a new minor line per the release guide: once merged, cut
release/3.1frommainso 3.1.0 is published — the kvant-api PR bumps itsquarkus-commons.versionto 3.1.0 and can only merge after that release exists.