In [[Thoughts on ArgoCD]] I had the following question > How to use your repository as the source of truth and git as more of a template storage? Well I'm making this post because I've thought about it a lot more as I've studied (and passed) my CKA and now looking into the security stuff I think I found a solution. It's not the best solution but it could definitely work. ## Set the scene You and your team are managing the pipeline for a bunch of apps. These apps are going to be deployed into a cluster using ArgoCD. The problem is the teams are using a different environment to test in so they write code with default test variables. You want to be able to override said variables for integration and prod environments. How do you handle this and keep things truly to GitOps standards? ## Possible Solution So what if you have a default values file in your repo. You can either dynamically create these files once al your test pass in the pipeline OR have a step in your pipeline that overrides certain variables. I'll pause here to say if you are using a mono-repo I think the best solution is to creat a root level values file that you can call on that has a minimum number of variables for you to override (container name and tag). Personally I like the override option, but a dynamically created file can be easy too if you have a template created. Honestly no right or wrong work around. I just wanted to express a solution I've been thinking about over the last week.