Hi all, is anyone successfully using the GIT integration in vRO? We are trying to implement it, but the functionality is confusing or counter intuitive, and I can't find any documentation on how it's supposed to actually work.
Today, we use LCM to migrate vRO objects between environments. But we are moving to the SaaS offering and would love to be able to retire our on-prem LCM and IDM boxes. If we can use the built-in git integration, that would be perfect.
We're not new to git, but we are new to the vRO implementation. Our plan was to do our dev in one vRO then push those changes to a branch, then merge that branch with master. Then in our prod vRO, we would pull from master. And maybe occassionally in the dev vRO we may discard any local changes and pull from master as well - as a sort of reset.
But we're finding that if we try to push a changed object to git, we start getting merge conflicts for objects we didn't select. We've also seen other behavior like a bunch of built-in workflows getting deleted during a Push. Not a pull, but while pushing.
And then we've seen a Pull not overwrite local objects with those in the git repository, which seems to defeat the purpose.
So for us, it doesn't seem like this implementation of git works at all like what we're used to. And we haven't even got to the complicated parts yet, e.g. syncing a config element so the IDs are the same between environments, but not syncing the attributes/variables because those are unique between environments.
Has anyone figured this out? Are there any resources out there that actually describe how this is supposed to work? Seems like yet another area where VMware is like "here's a neat thing....but we won't document it well, so good luck figuring out how it works". Or maybe it's just a checkbox so that they can say they have git integration even if it's not really a viable option.