From 59a0d97bc0bbc92f8933b0b52a1f3f457c61056b Mon Sep 17 00:00:00 2001 From: ximenchuifeng Date: Wed, 15 Jul 2026 00:28:05 +0800 Subject: [PATCH] docs(gitops): design disabling audit default deployment --- ...disable-audit-default-deployment-design.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/superpowers/specs/2026-07-15-disable-audit-default-deployment-design.md diff --git a/docs/superpowers/specs/2026-07-15-disable-audit-default-deployment-design.md b/docs/superpowers/specs/2026-07-15-disable-audit-default-deployment-design.md new file mode 100644 index 0000000..ff46a49 --- /dev/null +++ b/docs/superpowers/specs/2026-07-15-disable-audit-default-deployment-design.md @@ -0,0 +1,25 @@ +# Disable Audit Default Deployment + +## Goal + +Exclude the Audit service from the default MixingX demo deployment while keeping its Argo CD Application manifest and environment values available for a future manual re-enable. + +## Design + +- Move `applications/demo/audit.yaml` to `applications/demo/disabled/audit.yaml`. +- Keep `environments/demo/audit-values.yaml` unchanged. +- Keep the Audit image entry in `environments/demo/image-version.yaml` unchanged. +- Do not modify the Audit Helm chart or any other demo application. + +The demo root Application scans the active manifests directly under `applications/demo`. The repository already uses `applications/demo/disabled` for manifests that must not participate in the default deployment, so Audit will follow that convention. + +## Existing Cluster Behavior + +The root Application has `prune: false`. Moving the manifest prevents Audit from being created by a new/default deployment, but it does not delete an existing `mixingx-audit` Argo CD Application or its Kubernetes resources. Removing an already deployed instance is a separate operational action and is outside this change. + +## Verification + +- Confirm there is no Audit Application manifest directly under `applications/demo`. +- Confirm the manifest exists under `applications/demo/disabled` and remains valid YAML. +- Confirm the environment values and image-version entries remain present. +- Review the Git diff to ensure no unrelated deployment files changed.