Scenario: Couple of Atlas clusters are setup such that incremental export and import is setup via some custom program. Example, Cluster cl1 exports does incremental export and the output is imported into cluster cl2.
It may be worth while to maintain some information about the last successful import. This way the next incremental export will have correct parameters for its export.
- Create a new model, say AtlasSyncInfo, that stores information about top level entity used for export and the timestamp that should be used for subsequent incremental export.
- Utilize AtlasCluster's additionalInfo fields to store serialized version of AtlasSyncInfo.
- Provide REST APIs for retrieval of this information.