Replay — dev/replay

# Replay service config for `make dev-up` (examples/docker-compose.yaml). The
# replay service and its one-shot migration both use this file. Every setting
# is described in docs/operations/replay-service.md. Demonstrates explicit migrations,
# bounded operator-initiated retries, seven-day retention and separate
# capture/operator/metrics permissions against a local PostgreSQL database.
server:
  addr: ":8080"
  cors:
    allowed_origins: ["${REPLAY_CONSOLE_ORIGIN}"]
logging:
  level: info
metrics:
  enabled: true
  path: /metrics
  addr: ":9091"
database:
  url: "${REPLAY_DATABASE_URL}"
  max_conns: 10
core:
  control_url: "http://hookway:9092"
  control_token: "${REPLAY_CONTROL_TOKEN}"
retention:
  ttl: 168h
workers:
  concurrency: 4
  execution_timeout: 30s
  lease: 60s
keys:
  - name: core
    token: "${REPLAY_CAPTURE_TOKEN}"
    scopes: [capture]
  # The token you use in the console or curl: inspect, download and retry.
  - name: operator
    token: "${REPLAY_OPERATOR_TOKEN}"
    scopes: [read, payload, retry]
  # Prometheus scrapes with its own key: the scrape credential must not also
  # download payloads or trigger retries.
  - name: prometheus
    token: "${REPLAY_METRICS_TOKEN}"
    scopes: [metrics]