CMS-647: sync park-operation-sub-areas across environments #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira Ticket
CMS-647
Description
We are trying to sync subareas across environments. The goal is have every env match what prod has.
On a high level, there are 2 main operations going on for each environment.
We are also adding a global ID to subareas to make them easier to manage across envs.
To compare subareas across envs , we use the name and their "parent" park. It was verified using a separate script that no 2 subareas have the same name and the same parent park in any env.
So, if 2 subareas in different environments have the same name and same "parent" park, we can be sure that the objects refer to the same subarea.
All comparisons rely on the "parent" park of the subareas. Basically, the pseudocode would be 2 parts.
The actual code is different but it's the same idea.
There are few data structures that make the comparison easier and more efficient.
parksWithSubareas: