support custom request header from env / config #970
Merged
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.
closes: #308
As discussed in the issue above, there are use cases where being able to attach a custom header to every request is useful.
This introduces support for a new env var
CUSTOM_HEADER
, as well as a config block under defaults calledcustom_header
, that allows you to specify a string that is added directly as a request header to all outgoing requests. Note that this is not a key/value pair - this expects the formatkey: value
as a string.Testing:
Uploading a lib somewhere where we don't have permission:
Setting the env var:
Setting the config:
PTAL @jan-auer @mitsuhiko