# Split from gateway-kustomization.yaml on purpose: different change
# cadence (policies get tuned far more often than the Gateway itself gets
# recreated) and different blast radius (a bad policy build/prune can't
# touch the Gateway/DataPlane, and vice versa). Same GitRepository, same
# domain namespace, different path.
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: catalog-dev-api-gateway-policies
  namespace: flux-system
spec:
  interval: 10m
  sourceRef:
    kind: GitRepository
    name: k8s-platform
  path: ./dataplane-globalpolicy-template
  prune: true
  postBuild:
    substitute:
      NAME: catalog-dev
      NAMESPACE: catalog
      # Looked up manually after gateway-kustomization.yaml's
      # Gateway/GatewayConfiguration first reconciled — the operator
      # auto-names the mirrored KonnectGatewayControlPlane with a random
      # suffix, not derivable from NAME. See
      # dataplane-globalpolicy-template/global-policies-pluginbindings.yaml's
      # comment. Automate this lookup once the self-service pipeline exists.
      CONTROL_PLANE_REF_NAME: catalog-dev-bkphl
      # Every audience valid anywhere in the catalog domain — grows as the
      # domain gains APIs.
      JWT_AUDIENCE_WHITELIST: '["catalog-api", "mcp-catalog"]'
    substituteFrom:
      - kind: ConfigMap
        name: dataplane-template-defaults