feat: update api to be user-aware #70
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
mabdh
force-pushed
the
api-user-aware
branch
3 times, most recently
from
4a9c90f to
51ff646
Compare
mabdh
force-pushed
the
api-user-aware
branch
2 times, most recently
from
93de6be to
c95ee22
Compare
rahmatrhd
reviewed
Jan 26, 2022
mabdh
force-pushed
the
api-user-aware
branch
2 times, most recently
from
0b0b923 to
8e58d7f
Compare
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.
Currently require all APIs in
v1beta1to have identity headers (configurable via config)Columbus-User-Emailex:user@odpf.iov1API (that we want to remove) won't need that header