From 1429b5ae87355f46d1098a1bbd1e8ef73ce4d0a5 Mon Sep 17 00:00:00 2001 From: cluster-doctor-bot Date: Thu, 5 Feb 2026 01:44:30 +0000 Subject: [PATCH] fix: Correct ConfigMap field ordering in broken-aks-store-all-in-one.yaml Fixes ArgoCD sync failure for application 2-broken-apps (Issue #11) Root Cause: - ConfigMap 'rabbitmq-enabled-plugins' had incorrect field ordering - Fields were: apiVersion, data, kind, metadata (INVALID) - Should be: apiVersion, kind, metadata, data (VALID) This invalid structure caused Kubernetes API validation to fail during ArgoCD synchronization, resulting in 'one or more synchronization tasks are not valid' error. Impact: - Prevents deployment of the entire aks-store demo application - Blocks RabbitMQ StatefulSet and all dependent services Testing: - YAML syntax validated with PyYAML - Kubernetes manifest structure verified - 20 resource documents successfully parsed Related: #11 --- Act-3/argocd/apps/broken-aks-store-all-in-one.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Act-3/argocd/apps/broken-aks-store-all-in-one.yaml b/Act-3/argocd/apps/broken-aks-store-all-in-one.yaml index 0caf86d..46fc4de 100644 --- a/Act-3/argocd/apps/broken-aks-store-all-in-one.yaml +++ b/Act-3/argocd/apps/broken-aks-store-all-in-one.yaml @@ -61,12 +61,12 @@ spec: type: ClusterIP --- apiVersion: v1 -data: - rabbitmq_enabled_plugins: | - [rabbitmq_management,rabbitmq_prometheus,rabbitmq_amqp1_0]. kind: ConfigMap metadata: name: rabbitmq-enabled-plugins +data: + rabbitmq_enabled_plugins: | + [rabbitmq_management,rabbitmq_prometheus,rabbitmq_amqp1_0]. --- apiVersion: v1 kind: Secret