# catalog-info.yaml: describe this repository's service to ELOS (catalog as code).
# Put it at the root of the repository (or at .elos/catalog.yaml). ELOS reads it on every sync;
# the fields it sets are the source of truth for this service. Remove a field to manage it in ELOS.
apiVersion: elos/v1
kind: Service
metadata:
  description: Card payment authorisation and capture
  tags: [payments, pci]
  annotations:             # any key/value pairs; shown on the service page
    cost-center: CC-4020
    data-owner: finance
spec:
  type: service            # service | website | library | datastore | job
  tier: tier-1             # tier-1 (most critical) | tier-2 | tier-3
  lifecycle: production    # production | beta | deprecated
  system: Payments Platform
  domain: Payments
  language: Go
  frameworks: [grpc]
  owner: Payments          # a team name (one word), or a person's full name ("Priya Raman")
  providesApis: [payments.v1]
  consumesApis: [ledger.v1]
  links:
    - { kind: runbook, label: On-call runbook, url: https://wiki.example.com/payments/runbook }
    - { kind: dashboard, label: Latency, url: https://grafana.example.com/d/payments }