# Template of the railiance-platform add-on store. Prefer applying from:
#   ~/railiance-platform/argocd/platform-addons/openbao-secretstore/openbao-audit-core.clustersecretstore.yaml
#
# Do not apply until Secret external-secrets/openbao-audit-core-eso-token exists
# (scripts/openbao-eso-token-apply.sh). This store is KV-only: sender registry
# lives at platform/workloads/audit-core/senders. Database leases use the
# sibling store openbao-audit-core-database (engine path, not KV).
---
apiVersion: external-secrets.io/v1
kind: ClusterSecretStore
metadata:
  name: openbao-audit-core
  labels:
    app.kubernetes.io/part-of: railiance-gitops
    railiance-platform/component: external-secrets
    app.kubernetes.io/name: audit-core
spec:
  provider:
    vault:
      # In-cluster OpenBao on railiance01, not the public bao.coulomb.social UI.
      server: http://openbao.openbao.svc:8200
      path: platform
      version: v2
      auth:
        tokenSecretRef:
          name: openbao-audit-core-eso-token
          namespace: external-secrets
          key: token
  conditions:
    - namespaces:
        - audit-core
---
# Database engine, not KV. Same ESO token, different mount. Generators cannot
# read a token Secret from another namespace, so leases come through this
# store rather than VaultDynamicSecret.
apiVersion: external-secrets.io/v1
kind: ClusterSecretStore
metadata:
  name: openbao-audit-core-database
  labels:
    app.kubernetes.io/part-of: railiance-gitops
    railiance-platform/component: external-secrets
    app.kubernetes.io/name: audit-core
spec:
  provider:
    vault:
      server: http://openbao.openbao.svc:8200
      path: database
      version: v1
      auth:
        tokenSecretRef:
          name: openbao-audit-core-eso-token
          namespace: external-secrets
          key: token
  conditions:
    - namespaces:
        - audit-core