You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User request\n\nReplace bootstrap provisioning of each microservice as an independent Argo CD Application with a single Argo CD Application named platform that deploys all microservices together using the existing umbrella Helm chart in agynio/platform-charts (chart: ).\n\nConstraints:\n- Keep DBs as separate Argo CD Applications for now (no change to DB provisioning).\n- Keep current service naming (do not remove fullnameOverrides / do not rename services) to avoid breaking E2E immediately.\n- Address E2E/devspace stability by keeping autosync enabled for initial convergence, then disabling autosync centrally after bootstrap health check (no per-repo copy/paste steps).\n\n## Specification (from repo review)\n\n- Bootstrap currently creates many resources in and health scripts expect those names.\n- umbrella chart exists in and aggregates microservice charts as dependencies.\n- Main E2E risk with a single Argo Application is Argo automated sync/self-heal reverting deploy-from-source changes.\n- Argo CD supports disabling automated sync via .\n\n### Required changes\n\n1. In , replace per-microservice resources with a single named that deploys . Keep DB applications unchanged.\n2. Update to wait for the single application to reach Synced/Healthy (instead of waiting on a subset of microservice apps).\n3. Update to require (and other non-platform apps that remain separate) and stop requiring individual microservice app names.\n4. Add a script to disable autosync for the application by patching .\n5. In , run the autosync-disable script after the platform health verification step so CI users don’t need per-repo sync toggling.\n\n### Acceptance criteria\n\n- Bootstrap provisions the platform microservices via a single Argo CD Application named .\n- DB apps remain separate Argo apps as before.\n- Provision action still converges to a healthy cluster.\n- After health verification, Argo automated sync is disabled for , preventing reverts of deploy-from-source patches.\n- Existing E2E suites continue to function without updating service DNS names.
User request\n\nReplace bootstrap provisioning of each microservice as an independent Argo CD Application with a single Argo CD Application named platform that deploys all microservices together using the existing umbrella Helm chart in agynio/platform-charts (chart: ).\n\nConstraints:\n- Keep DBs as separate Argo CD Applications for now (no change to DB provisioning).\n- Keep current service naming (do not remove fullnameOverrides / do not rename services) to avoid breaking E2E immediately.\n- Address E2E/devspace stability by keeping autosync enabled for initial convergence, then disabling autosync centrally after bootstrap health check (no per-repo copy/paste steps).\n\n## Specification (from repo review)\n\n- Bootstrap currently creates many resources in and health scripts expect those names.\n- umbrella chart exists in and aggregates microservice charts as dependencies.\n- Main E2E risk with a single Argo Application is Argo automated sync/self-heal reverting deploy-from-source changes.\n- Argo CD supports disabling automated sync via .\n\n### Required changes\n\n1. In , replace per-microservice resources with a single named that deploys . Keep DB applications unchanged.\n2. Update to wait for the single application to reach Synced/Healthy (instead of waiting on a subset of microservice apps).\n3. Update to require (and other non-platform apps that remain separate) and stop requiring individual microservice app names.\n4. Add a script to disable autosync for the application by patching .\n5. In , run the autosync-disable script after the platform health verification step so CI users don’t need per-repo sync toggling.\n\n### Acceptance criteria\n\n- Bootstrap provisions the platform microservices via a single Argo CD Application named .\n- DB apps remain separate Argo apps as before.\n- Provision action still converges to a healthy cluster.\n- After health verification, Argo automated sync is disabled for , preventing reverts of deploy-from-source patches.\n- Existing E2E suites continue to function without updating service DNS names.