Two separate discussions in same thread (with a title that doesn’t reflect any of them), not the best way, but because we have started it
Replying to comments about RFC:
3. For both Accounts and TagSets we use them different between our two instances, so we don’t have any global. But I can understand other scenarios where you have global accounts/tagsets.
And regarding our merge solution:
We started to use the Migrator and from the beginning we only removed Accounts and TagSets, a way that is mentioned here: https://octopus.com/docs/administration/data-migration
“Transfer it to a new Octopus Server - You can delete files you don’t want to import (e.g., if you’re transferring one project, just delete everything except the files for that project)”
Also we found recommendations of Migrator to keep instances in sync here https://octopus.com/docs/deployment-patterns/isolated-octopus-deploy-servers.
“The migration tool could be reused periodically to keep both servers in sync. Because the resulting export is simply a collection of JSON files in folders, a source control system like Git could be used for this purpose. Any imports subsequent to the initial import would result in a merge of any changes.”
And with discussions with you it felt like a good solution. But, like I said, from the beginning we didn’t know all the things that didn’t work out.
So during our setup we have ran in to things we needed to fix to be able to automate a continuously sync between our instances. Because of that our MergeApplication has grown during implementation. During this period we haven’t really looked into/thought about other alternatives, because we have been able to solve things, step by step.
Now when we (think) we know what we have to do I guess its good to look at alternatives before going live with it. Do you think we can get this working with API and C# SDK? That would probably be a more solid solution. One thing to have in mind is that our two instances cannot communicate with each other (but can get packages from the same external NuGet feed).
I appreciate all feedback and are happy to give input regarding RRP. We could have a screenshare to look at it more hands on.