4 ms·
This is correct. If it helps, you can think of your terraform files as HEAD and the state file as HEAD~1
by baby_souffle 3y ago
This is correct.
If it helps, you can think of your terraform files as HEAD and the state file as HEAD~1
- verdverm 3y agoHow are multiple branches handled? How would locking and conflict resolution work? Imagine two branches trying to update staging using gitops
- jen20 3y agoThey aren’t handled - the reality of the situation is that the subversion model is better suited to infrastructure than Git.
- oneplane 3y agoOnly if the infrastructure you target has no concepts of versions, and if it only has monolithic environments (which still holds true for much of the older infrastructure). But if we just take the GitOps branches problem, they are indeed not handled, but that's because you generally configure your GitOps pipeline to only allow interaction from a specific ref, not any branch you might have lying around ;-) The SVN version would either be trunk-based deployments or revision-based, where you have to tell your reconciler which revision you want.
- jen20 3y agoIt’s because infrastructure largely does not have the concept of versioning, and branching infrastructure just makes no sense.