cloudfoundry / cloudfoundry/cf-java-client

Tracking Request/Response for Cloud Foundry Calls

Open
#1,141 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement question triaged
Dominant language
Java
Stars
334
Forks
319
PR merge metrics
No merged PRs in 30d

Description

Requirement: Passing cloud foundry user related data from the application with each cloud foundry requests and need to send the respective response headers back to the calling application.

For Example: For Creating a Service Key, the code flow will be

Application ----> Mono createServiceKey(CreateServiceKeyRequest request) ----> Mono requestCreateServiceKey ----> Mono create(CreateServiceKeyRequest request) ----> Mono post(Object requestPayload, Class responseType, Function<UriComponentsBuilder, UriComponentsBuilder> uriTransformer) ----> Http Client (for HTTP Related Operations)

Is there any way from which we can track the Http Client Response Headers from the calling application.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the createServiceKey → requestCreateServiceKey → create → post flow named in the issue and inspect how the HTTP client handles response headers. Define a supported way for the calling application to receive those headers and verify it across this flow; done means the respective Cloud Foundry response headers are available to the caller.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.