Replies: 1 comment
-
Never mind, I found the functionality and it already exists. I just need to set SyncDirection on the SetupTable objects in my SyncSetup's Tables property. Example: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
EDIT: I discovered this functionality already exists, see next post for how to use
We'd like to use this to populate test environments in a one-way manner. (Changes from the main server will get copied to the test environment, but changes to the test environment will never be copied back to the main server.)
Looking at the code, it should be fairly easy to add a property to the SyncSetup object that would be checked in the RemoteOrchestrator.ApplyChanges's InternalApplyThenGetChangesAsync method to skip applying changes to the server. I can certainly do a pull request for this feature.
Before I mess with this, I'm not missing any existing way to do a one-way sync, right? (I thought earlier when looking at this library that it had this feature. Now that I want to implement it, I can't find anything.)
Would there be any need to support one-way synching OTHER THAN making the server (remoteorchestrator) be the read-only partner? I don't think there is any reason to allow the client (localorchestrator) to be the read-only partner. (Just flip the client/server to get the direction you want rather than adding a direction property)
Beta Was this translation helpful? Give feedback.
All reactions