This repository has been archived by the owner on Jul 23, 2020. It is now read-only.
config option to enable GDPR compliant API #236
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
|
Can you add a description of this function to README? |
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.
As we know, Atlassian is in the process of changing and deprecating some API behavior to better comply with GDPR, they started by removing personal user data and adding accountIds instead.
Some APIs still return old user data but we can't know for sure when APIs will be completely changed.
Luckily, Atlassian has provided us with a way to test these changes and prepare.
This can be done by sending an HTTP header alongside requests (see here), which this PR enables.
You can read here for other changes being performed, although it seems the announcement is pretty old