Full Cluster Promotion

[deas]

I am trying to establish a promotion pipeline using a Monorepo structurally similar to the Monorepo documented. I have a single ArgoCD installation per Stage/Cluster covering all applications and the entire cluster using a Root Application, App of Apps and ApplicationSet. I am trying to start using a simple Pipeline covering this whole thing. The model uses a single main branch and maps stages using folders, adding, changing and removing bits as needed.

Aiming at simplicity, the current implementation allows the team to freely commit to the test stage and ArgoCD auto syncing everything. Now, I want a manual promotion process of all changes, once when we are happy with the test stage as a whole, so I came up with a Warehouse using a single git Subscription. I am now wondering how to move on. It looks like I need some very custom logic. Looking at the Promotion Steps Reference, it appears the http step can help out. If this is the way to move forward, I think I'd likely want to introduce a sidecar container providing the implementation to make the changes to the git working tree?

I understand there are tradeoffs when choosing how to map stages. Last time I worked on a similar scenario (years ago), I intuitively chose to map stages using branches because promotion appeared so easy.

Anyone willing to share experiences or suggestions with a Monorepo Layout and a single Warehouse creating Freight to sync entire clusters?

[deas]

Sorry, missed this response.