The idea behind this is to be able to keep the same uid in an environment.
This becomes necessary when we want to track modifications made on trees, as the diff between 2 jsons with different uids is a mess to deal with.
The idea is to keep the UIDs only in dev environment, but to push to nondev without keeping the same ones.
Let's say X and Y are working on bug fixes and new features on the same trees, they both use the same uids and they commit with the same uids.
The jsons are then pushed to a git repo and it becomes easy to track modifications.
When they update their environment, they use the -k option to update trees.
When we validate their changes, we push them to nondev environments without the -k options. This way we don't rely on uids except for dev.
Hi,
The idea behind this is to be able to keep the same uid in an environment. This becomes necessary when we want to track modifications made on trees, as the diff between 2 jsons with different uids is a mess to deal with. The idea is to keep the UIDs only in dev environment, but to push to nondev without keeping the same ones. Let's say X and Y are working on bug fixes and new features on the same trees, they both use the same uids and they commit with the same uids. The jsons are then pushed to a git repo and it becomes easy to track modifications. When they update their environment, they use the -k option to update trees. When we validate their changes, we push them to nondev environments without the -k options. This way we don't rely on uids except for dev.
What do you think?
Regards,
Ben