Last updated 2026-07-01

adb-tickets

AI-generated content

This document was generated by an AI assistant. Verify accuracy before relying on the details.

Role

Service that manages tickets / interventions: reports, maintenance requests, intervention tracking on properties. Includes a ticket-events system that records the history.

Status in the monorepo

Item	State
Top-level folder	✓ `adb-tickets/`
Root Maven aggregator	✓ `<module>adb-tickets</module>`
FQDN defined in `adb-common`	✓ `TICKETS = http://adb-tickets`
Helm chart	✓ `adb-charts/charts/services/templates/adb-tickets.yaml`
Ingress route	✓ `/tickets`
Nginx route (`adb/proxy/`)	✓ `location /tickets`
Associated doc	✓ `technical-epics/tickets/i-have-ticket-details.md`
Artillery tests	✓ ticket creation scenarios
Listed in release script	✓

Connections

flowchart LR
    tickets[adb-tickets]

    aggregates[adb-aggregates] -->|TicketsClient<br/>GET /tickets?q=...| tickets
    views[adb-views] -.SQS<br/>onTicketModified<br/>onTicketEventModified.-> tickets

    adbgraph[adb-graph] -. "RabbitMQ<br/>tickets.graph" .-> tickets

    ui[adb-ui] -->|/tickets/...| tickets
    web[adb-web/bff] --> tickets

    notes[/notes route<br/>deprecated/] -.redirect.-> tickets

Consumers

adb-aggregates: calls GET /tickets?q=... for cross-service search (via TicketsClient in adb-common).
adb-views: consumes the onTicketModified and onTicketEventModified events through SQS to maintain dashboard projections.
adb-graph: consumes RabbitMQ events via the adb-tickets-x exchange (queue tickets.graph).
adb-ui / adb-web: direct calls through the gateway.

Outbound dependencies

The source code now lives in adb-tickets/. Document controllers, data model, and outbound dependencies from the code in a follow-up ingest.

Migration from adb-notes

During release R4, the notes feature was migrated to adb-tickets:

MongoDB data exported from adb-notes then imported into adb-tickets.
Kubernetes service adb-notes removed.
Ingress route /notes now redirects to adb-tickets.

See adb-notes for the details.

RabbitMQ configuration (legacy)

Documented in adb-charts/mq.md:

Exchange: adb-tickets-x (headers exchange).
Consumer: adb-graph via the queue tickets.graph.
DLX: adb-tickets-dlx.

Configuration & deployment

Helm chart adb-charts/charts/services/templates/adb-tickets.yaml:

Docker image: lifeconnect/adb-tickets
Standard env variables (MongoDB URI, Keycloak, AWS).
AWS messaging clients use Spring Cloud AWS region and credential providers, SNS DLQ forwarding, and the shared AWS_ENDPOINT_URL override used by the local stack.

To do

[ ] Document the controllers and the data model once the code is available.