remove variable metadata API endpoints #8192
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
Both of these have been removed:
- /api/access/variable/{varId}/metadata/ddi:
- /api/meta/variable/{varId}:
See IQSS/dataverse-security#43
pdurbin
added a commit
to QualitativeDataRepository/dataverse
that referenced
this pull request
Nov 16, 2021
Conflicts (from PR IQSS#8192 it seems): src/main/java/edu/harvard/iq/dataverse/api/Access.java
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.
What this PR does / why we need it:
Both of these have been removed:
Which issue(s) this PR closes:
Closes https://github.com/IQSS/dataverse-security/issues/43
Special notes for your reviewer:
See issue.
Suggestions on how to test this:
See issue.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No.
Is there a release notes update needed for this change?:
Perhaps. Let's discuss.
Additional documentation:
No.