Adding support for custom headers #207
Merged
Conversation
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
karenzone
reviewed
Jul 23, 2024
Contributor
karenzone
left a comment
karenzone
left a comment
There was a problem hiding this comment.
Left a comment inline for your consideration.
Co-authored-by: Karen Metts <35154725+karenzone@users.noreply.github.com>
jsvd
reviewed
Dec 17, 2024
jsvd
reviewed
Dec 17, 2024
jsvd
added a commit
that referenced
this pull request
Dec 18, 2024
This was referenced Jan 13, 2025
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.
This adds support for custom headers to be specified in the input configuration and included in transport options.
custom_headers => {"Header Name" => "Value"}