This repository was archived by the owner on Dec 1, 2024. It is now read-only.
Data-configuration: introduce ingress/egress data slices #235
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jordigilh
force-pushed
the
add_bidirectional_data_transfer
branch
from
0e0ae10 to
c070794
Compare
jordigilh
changed the title
jordigilh
force-pushed
the
add_bidirectional_data_transfer
branch
from
4df7cd3 to
7574379
Compare
gabriel-farache
approved these changes
May 25, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes in the swagger for data-configuration to allow specifying egress (existing) or ingress data synchronization on the worker.