feat(phoenix/tenant-portal#413): record the request's azp on the revision #245

Merged
jorge.bornhausen merged 2 commits from feat/revision-azp into main 2026-10-23 18:42:12 +00:00

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

  • quarkus-tracing-service: TracingConstants.AZP MDC key (azp) and TracingService.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).
  • quarkus-audit-tools: Revision.azp column (revinfo), RevisionContextProvider.getAzp(), the DefaultRevisionContextProvider implementation and the AuditRevisionListener wiring — the same pattern as every other context field.
  • Test migration V4__add_revision_azp.sql and 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.1 from main so 3.1.0 is published — the kvant-api PR bumps its quarkus-commons.version to 3.1.0 and can only merge after that release exists.

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 - **quarkus-tracing-service**: `TracingConstants.AZP` MDC key (`azp`) and `TracingService.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). - **quarkus-audit-tools**: `Revision.azp` column (`revinfo`), `RevisionContextProvider.getAzp()`, the `DefaultRevisionContextProvider` implementation and the `AuditRevisionListener` wiring — the same pattern as every other context field. - Test migration `V4__add_revision_azp.sql` and 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.1` from `main` so 3.1.0 is published — the kvant-api PR bumps its `quarkus-commons.version` to 3.1.0 and can only merge after that release exists.
feat(phoenix/tenant-portal#413): record the request's azp on the revision
All checks were successful
Build / build (pull_request) Successful in 7m14s
816342387f
Add the azp MDC key to the tracing service and record it as a new revinfo
column via the revision-context provider, next to the actor.

Refs phoenix/tenant-portal#413
docs: tighten the azp mdc key comment
All checks were successful
Build / build (pull_request) Successful in 3m0s
d24ac13fce
Refs phoenix/tenant-portal#413
jorge.bornhausen deleted branch feat/revision-azp 2026-10-23 18:42:12 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
phoenix-oss/quarkus-commons!245
No description provided.