# Staging overrides. Everything else inherits values.yaml.
# Pinned explicitly (not left to release-name defaults) so the two envs
# provably never share a namespace, ALB, or cluster-scoped store.
namespace: planpal-staging

image:
  frontend:
    tag: latest
  backend:
    tag: latest

externalSecrets:
  storeName: staging-aws-planpal
  # ponytail: staging points at the SAME planpal/* SM keys as prod for now.
  # Give staging its own DB/config by pointing these at planpal-staging/* keys
  # and letting the ESO role read them.
  secrets:
    backend-env: planpal/backend-env
    aws-env: planpal/aws-env
    seed-env: planpal/seed-env
    frontend-env: planpal/frontend

ingress:
  host: staging.fakhri-k8.sandbox.devopsinstitute.id
  certArn: arn:aws:acm:ap-southeast-3:134604498185:certificate/5d0f65f5-9d93-4c2e-87db-b9afe8972048
  groupName: planpal-staging   # own ALB, separate from prod and the old live release

# Seed the admin on staging too. Flip to false once seeded.
seedJob:
  enabled: true