AgileWebs/customer-orders-bff
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
7eec502b5b
customer-orders-bff/docs/runbooks/containerization.md
José René White Enciso a235d264bf feat(customer-orders): add order edge flow 
Why: baseline pending customer order edge handlers and runtime assets before security wave.

What: add submit order contracts/handlers, service adapter updates, and docs/docker assets.

Rule: keep technical intent and align repository workflow.
2026-03-08 15:00:08 -06:00

1.1 KiB
Raw Blame History

Containerization Runbook

Image Build

If the repo consumes internal packages from Gitea, pass feed credentials as build args.

docker build   --build-arg NUGET_FEED_USERNAME=<gitea-login>   --build-arg NUGET_FEED_TOKEN=<gitea-token>   -t agilewebs/customer-orders-bff:dev .

Local Run

docker run --rm -p 8080:8080 --name customer-orders-bff agilewebs/customer-orders-bff:dev

Health Probe

  • Path: /health
  • Fallback path: /healthz
  • Port: 8080

Runtime Notes

  • Exposes REST edge endpoints for customer order lifecycle flows.

Health Endpoint Consistency

  • Canonical probe: /health
  • Compatibility probe: /healthz
  • Container port: 8080

Demo Integration

  • Participates in: restaurant demo compose stack.
  • Integration artifact path: greenfield/demo/restaurant/docker-compose.yml

Known Limitations

  • Current runtime adapters are still predominantly in-memory for deterministic local/demo behavior.
  • Demo PostgreSQL seeds validate integration contracts and smoke determinism, but do not yet imply full persistence implementation parity.