Add support for GA4GH service info query #482
Merged
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.
This adds an initializer in
config/initializers
that will run at boot. It expects to find adata_version.yml
at the root dir of the application. That file should contain a keyversion
containing the current data version.This will be loaded into a constant.
When generating a new data release, you will need to remember to update this value (so, if there are docs for the process somewhere, may be good to add this step to them). Its manual for now, but as we automate the data generation process, we should automate this too.
Additionally, I have added a top level
serviceInfo
query to the API containing all the fields needed for the GA4GH Service discovery spec. Though the query obviously looks different given it is GraphQL rather than REST, the response should be compliant with their schema.updated_at
andversion
information for this is pulled live from GitHub. (dataVersion
is still handled as described above)The query
Will yield
closes #481