feat: Extract cadence-caller-type from headers#7644
Merged
fimanishi merged 1 commit intocadence-workflow:masterfrom Jan 28, 2026
Merged
feat: Extract cadence-caller-type from headers#7644fimanishi merged 1 commit intocadence-workflow:masterfrom
fimanishi merged 1 commit intocadence-workflow:masterfrom
Conversation
Signed-off-by: fimanishi <fimanishi@gmail.com>
fimanishi
requested review from
3vilhamster,
Shaddoll,
davidporter-id-au,
demirkayaender,
dkrotx,
jakobht,
neil-xie,
sankari165,
shijiesheng and
taylanisikdemir
as code owners
davidporter-id-au
approved these changes
Jan 27, 2026
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
2 participants
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 changed?
Created ways to extract CallerInfo headers, such as cadence-caller-type, and either return CallerInfo or return a context with the CallerInfo in it.
If cadence-caller-type is not provided or is an empty string, the value assigned is "unknown".
Why?
We want to categorize caller types for auditing and rate limiting purposes.
We should be able to add CallerInfo to the context so it can propagate downstream as well as being able to extract directly from headers when that's not necessary.
How did you test it?
Unit tests.
Potential risks
No risks.
Release notes
Documentation Changes