chore: use vector endpoint for MVI API calls #373
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
pratik151192
commented
Aug 28, 2023
| _CONTROL_ENDPOINT_CLAIM_ID = "cp" | ||
| _CACHE_ENDPOINT_CLAIM_ID = "c" | ||
| _VECTOR_ENDPOINT_CLAIM_ID = "c" |
There was a problem hiding this comment.
we dont have a new claim here so defaulting to c
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.
For MVI data plane calls, we were using
cacheas the endpoint prefix; this PR updates it to usevector. Note that for legacy tokens, we do not have a new JWT claim, so we will be usingcacheas the prefix for that as well.Also, for control plane operations, the endpoint prefix is still
control.