0

I'm converting our existing deployment process to ArgoCD and using our existing helm chart but I'm not sure how to handle our existing hooks due to Argo not having as many as helm does. We have three environments, and one of which (QA) is used to deploy disposable apps, created for a pull request. When these apps are first deployed, we have two post-install hooks to create and see the database. Unfortunately, Argo (understandably) doesn't have a concept of install or upgrade so there's no direct translation to an Argo hook. I'm not sure how to proceed.

Is there a way of having a hook run once on the initial sync but never run again? The only thing I can think of is to modify the code to check if the DB has been seeded already and do nothing if so, but was hoping to find a way of doing it purely in the configuration

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.