-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backend-aware collection whitelisting #139
Comments
soxofaan
added a commit
that referenced
this issue
Apr 2, 2024
soxofaan
added a commit
that referenced
this issue
Apr 2, 2024
soxofaan
added a commit
that referenced
this issue
Apr 2, 2024
soxofaan
added a commit
that referenced
this issue
Apr 2, 2024
soxofaan
added a commit
that referenced
this issue
Apr 2, 2024
soxofaan
added a commit
that referenced
this issue
Apr 2, 2024
soxofaan
added a commit
that referenced
this issue
Apr 3, 2024
soxofaan
added a commit
that referenced
this issue
Apr 3, 2024
backend aware white listing is now active on CDSE aggregator (staging) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
related to #129 and #137 :
collection whitelisting/merging should be backend-aware
e.g. when combining backend1 and backend2, and both have collection S2, it should be possible to configure that only S2 of backend2 should be considered, and backend1 should completely skipped, both for metadata merging and process dispatching
The text was updated successfully, but these errors were encountered: