feat: update custom webhook headers #1908
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
JeevaRamu0104
added
the
S-blocked
|
Review changes with |
JeevaRamu0104
added
S-waiting-on-review
kanikabansal-juspay
approved these changes
Dec 12, 2024
sagarnaikjuspay
approved these changes
Dec 12, 2024
github-actions
bot
added
Closed
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.
Type of Change
Description
Screen.Recording.2024-12-12.at.11.03.15.AM.mov
Allow user to update masked custom HTTP headers.
Motivation and Context
Custom Https headers will be masked.On update allow user to enter the new value
How did you test it?
Configure a webhook url under payment setting and then configure the custom http headers.
Where to test it?
Checklist
npm run re:build