This repository has been archived by the owner on Dec 16, 2019. It is now read-only.
Handling stable IDs from CentralEGA. #263
Merged
Conversation
This file contains 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
viklund
pushed a commit
that referenced
this pull request
Nov 22, 2018
Handling stable IDs from CentralEGA.
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.
CentralEGA uses their own IDs to identify files. These IDs are assumed unique and we receive them in the broker message.
We only add them to our database for information. For each EGA-id, we internally use another locally managed unique ID.
We add in this PR, an endpoint to translate the EGA-id into a vault filepath. The endpoint is temporarily added to the keyserver, since the data-out-api is already accessing it. This will not be the case in the future.