smartcontractkit / smartcontractkit/chainlink
[FEAT] Update Bridge task
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.2k
- Forks
- 2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 202
Description
Description
Please add the possibility of adding headers param to the Bridge Task.
Motivation
Unfortunately, this working only for the HTTP Task, and is very lacking for Bridge Task. This is a necessary feature if the requested resource requires an authorization header, for example: x-api-key: testkey. It may also be important to use this for your backend service, in order to limit the possibility of calling the endpoint only by a Chainlink node.
Additional Information
Bridge Task doc – https://docs.chain.link/chainlink-nodes/oracle-jobs/task-types/task_bridge
HTTP Task doc – https://docs.chain.link/chainlink-nodes/oracle-jobs/task-types/task_http
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Bridge Task and HTTP Task documentation to understand the existing parameters and expected header behavior. The work is done when Bridge Task requests support an authorization header such as x-api-key, with the behavior documented and verified against the relevant task tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100