Support HTTP headers on InvokeFunctionRequest/InvokeFunctionResponse
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 243
- Forks
- 171
- Avg merge
- 30m
- Merged PRs (30d)
- 4
Description
Cloud functions support sending and receiving HTTP headers when invoking functions. The Java SDK does not currently expose setting HTTP headers on InvokeFunctionRequest or getting them off InvokeFunctionResponse.
As a workaround for sending headers, the invocationCallback can be used to indirectly set headers. There is no such workaround for accessing response headers.
It looks easy enough to add in support. Getting headers off responses for example, the information is already on hand and would just need to be added onto: InvokeFunctionRequest.Builder & InvokeFunctionRequest
I'm looking into the feasibility of adding in support for these. Is this something that would be a welcomed contribution?
Thanks
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 bmc-functions/src/main/java/com/oracle/bmc/functions/internal/http/InvokeFunctionConverter.java around line 89, then inspect InvokeFunctionRequest.Builder, InvokeFunctionRequest, and InvokeFunctionResponse. Done means the Java SDK exposes HTTP headers for sending with requests and retrieving from responses, without relying on the invocationCallback workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100