# Tracked copy of the live `medical-chatbot-data` Application (k3s, personal
# ArgoCD instance at argocd.realvuxbaro.me). Verified against the live object
# 2026-08-18 — every field below matches `status.sync.status: Synced`,
# `status.health.status: Healthy`.
#
# Owns PostgreSQL and Qdrant only (the 15,100-point corpus and query
# history). Deliberately a separate Application from medical-chatbot-app so
# that an app-side sync failure, prune, or rollback can never delete the
# PersistentVolumeClaims — see values-production-data.yaml.
#
# Unlike medical-chatbot-app, the live Application carries no inline
# `spec.source.helm.values` at all: this release has no image tag CI rewrites
# and no secret, so it is already fully represented by this file plus
# values.yaml + values-production-data.yaml. Applying this file for disaster
# recovery needs no follow-up step.
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: medical-chatbot-data
  namespace: argocd
spec:
  project: default
  source:
    repoURL: https://github.com/BaoVu2k4/vsf-duocthu.git
    targetRevision: master
    path: infra/helm/medical-chatbot
    helm:
      valueFiles:
        - values.yaml
        - values-production-data.yaml
  destination:
    server: https://kubernetes.default.svc
    namespace: medical-chatbot-data
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true