Updates datasource_item with new fields #705
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Datasource item has been updated to support some new fields. Below are the 6 new fields and the endpoints it affects:
ask_data_enablement: publish, update, get_by_id
description: publish, get, get_by_id (only returned if it's set to something)
encrypt_extracts: update, get, get_by_id
has_extracts: get, get_by_id (2020.2+, v3.8+ with next MR)
use_remote_query_agent: publish, get, get_by_id
webpage_url: get, get_by_id
This change also alphabetizes the fields in datasource_item to make it a bit more readable. Doc updates coming