Add support for hook call headers #80
Open
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
- add different hook action variants - pass headers to hook - refactor hook file structure
- to follow `serde_yaml` version switch
- split hook action config and main logic to allow initializing a re-usable client - update `HookAction` initialization - replace `call_hook` test impl with `wiremock`
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.
PR can be reviewed, but is intended to be merged after the 0.2 release.
Description
PR extends the hook configuration to allow configuring header, that will be used in the requests made to the hook server. A hook action can now be configured either as a URL or as a mapping with the fields
urlandheaders.Smaller other things refactored:
indoc, to make serialized examples more readableHookActioninitialization.initializehook_call_testimport withwiremock