rea
Reverse engineer anything with agents, from app behavior down to native binaries.
- 468k
- TypeScript
- MIT
- 2 min ago
Java Client Library for Cloud Foundry
Repo cloudfoundry/cf-java-client, read from GitHub 1 min ago. cloudfoundry has not joined Take My Repo.
cloudfoundry/cf-java-client is a public repo on GitHub by cloudfoundry. Java Client Library for Cloud Foundry. It declares the Apache-2.0 license on GitHub. It is written mainly in Java, has 336 stars and last changed on 2026-11-17. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-18.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
| Artifact | Javadocs |
|---|---|
cloudfoundry-client |
|
cloudfoundry-client-reactor |
|
cloudfoundry-operations |
|
cloudfoundry-util |
The cf-java-client project is a Java language binding for interacting with a Cloud Foundry instance. The project is broken up into a number of components that expose different levels of abstraction depending on need.
cloudfoundry-client – Interfaces, request, and response objects mapping to the Cloud Foundry REST APIs. This project has no implementation and therefore cannot connect to a Cloud Foundry instance on its own.cloudfoundry-client-reactor – The default implementation of the cloudfoundry-client project. This implementation is based on Reactor Netty HttpClient.cloudfoundry-operations – An API and implementation that corresponds to the Cloud Foundry CLI operations. This project builds on the cloudfoundry-client and therefore has a single implementation.The Cloud Foundry Java Client has two active versions. The 6.x line includes breaking changes (see below), while the 5.x line maintains backward compatibility.
DopplerClient.recentLogs() — Recent Logs via DopplerWarning
Removed since cf-java-client 6.0.x
The DopplerClient.recentLogs() endpoint (and the related RecentLogsRequest / LogMessage types from the org.cloudfoundry.doppler package) have been removed.
This API relied on the Loggregator Doppler/Traffic Controller endpoint /apps/{id}/recentlogs, which was removed in Loggregator ≥ 107.0.
The affected platform versions are:
| Platform | Last version with Doppler recent-logs support |
|---|---|
| CF Deployment (CFD) | < 24.3 |
| Tanzu Application Service (TAS) | < 4.0 |
Migration: Replace any call to DopplerClient.recentLogs() with LogCacheClient.read() (available via org.cloudfoundry.logcache.v1.LogCacheClient).
// Before (deprecated) dopplerClient.recentLogs(RecentLogsRequest.builder() .applicationId(appId) .build()); // After logCacheClient.read(ReadRequest.builder() .sourceId(appId) .envelopeTypes(EnvelopeType.LOG) .build());
The return type and envelope objects differ between the two APIs:
Doppler (org.cloudfoundry.doppler) |
Log Cache (org.cloudfoundry.logcache.v1) |
|
|---|---|---|
| Return type | Flux<Envelope> |
Mono<ReadResponse> → unpack via response.getEnvelopes().getBatch() |
| Log access | envelope.getLogMessage() → LogMessage |
envelope.getLog() → Log |
| Message text | logMessage.getMessage() |
log.getPayloadAsText() |
| Message type | MessageType.OUT / ERR |
LogType.OUT / ERR |
| Source metadata | logMessage.getSourceType(), .getSourceInstance() |
envelope.getTags().get("source_type"), envelope.getInstanceId() |
See the [org.cloudfoundry.doppler][doppler-pkg] and [org.cloudfoundry.logcache.v1][logcache-pkg] Javadoc for full type details.
Note
Operations API users: Use Applications.logs(ApplicationLogsRequest) instead of the removed Applications.logs(LogsRequest).
Applications.logs(LogsRequest) — RemovedWarning
Removed since cf-java-client 6.0.x
The Applications.logs(LogsRequest) method (and the LogsRequest type) have been removed.
Migration: Use Applications.logs(ApplicationLogsRequest) instead. For recent logs, set recent(true) (the default). For streaming, set recent(false).
Most projects will need two dependencies; the Operations API and an implementation of the Client API. For Maven, the dependencies would be defined like this:
<dependencies> <dependency> <groupId>org.cloudfoundry</groupId> <artifactId>cloudfoundry-client-reactor</artifactId> <version>latest.RELEASE</version> </dependency> <dependency> <groupId>org.cloudfoundry</groupId> <artifactId>cloudfoundry-operations</artifactId> <version>latest.RELEASE</version> </dependency> ... </dependencies>
Snapshot artifacts can be found in the Spring snapshot repository:
<repositories> <repository> <id>spring-snapshots</id> <name>Spring Snapshots</name> <url>https://repo.spring.io/snapshot</url> <snapshots> <enabled>true</enabled> </snapshots> </repository> ... </repositories>
For Gradle, the dependencies would be defined like this:
dependencies {
compile 'org.cloudfoundry:cloudfoundry-client-reactor:<latest>.RELEASE'
compile 'org.cloudfoundry:cloudfoundry-operations:<latest>.RELEASE'
...
}Snapshot artifacts can be found in the Spring snapshot repository:
repositories {
maven { url 'https://repo.spring.io/snapshot' }
...
}Both the cloudfoundry-operations and cloudfoundry-client projects follow a "Reactive" design pattern and expose their responses with Project Reactor Monoss and Fluxs.
CloudFoundryClient, DopplerClient, UaaClient BuildersNote
DopplerClient — partial deprecation: The recentLogs() method on DopplerClient is deprecated and only works against Loggregator < 107.0 (CFD < 24.3 / TAS < 4.0). See the Deprecations section above for the migration path to LogCacheClient.
The lowest-level building blocks of the API are ConnectionContext and TokenProvider. These types are intended to be shared between instances of the clients, and come with out of the box implementations. To instantiate them, you configure them with builders:
DefaultConnectionContext.builder() .apiHost(apiHost) .build(); PasswordGrantTokenProvider.builder() .password(password) .username(username) .build();
In Spring-based applications, you'll want to encapsulate them in bean definitions:
@Bean DefaultConnectionContext connectionContext(@Value("${cf.apiHost}") String apiHost) { return DefaultConnectionContext.builder() .apiHost(apiHost) .build(); } @Bean PasswordGrantTokenProvider tokenProvider(@Value("${cf.username}") String username, @Value("${cf.password}") String password) { return PasswordGrantTokenProvider.builder() .password(password) .username(username) .build(); }
CloudFoundryClient, DopplerClient, and UaaClient are only interfaces. Each has a Reactor-based implementation. To instantiate them, you configure them with builders:
ReactorCloudFoundryClient.builder() .connectionContext(connectionContext) .tokenProvider(tokenProvider) .build(); ReactorDopplerClient.builder() .connectionContext(connectionContext) .tokenProvider(tokenProvider) .build(); ReactorUaaClient.builder() .connectionContext(connectionContext) .tokenProvider(tokenProvider) .build();
In Spring-based applications, you'll want to encapsulate them in bean definitions:
@Bean ReactorCloudFoundryClient cloudFoundryClient(ConnectionContext connectionContext, TokenProvider tokenProvider) { return ReactorCloudFoundryClient.builder() .connectionContext(connectionContext) .tokenProvider(tokenProvider) .build(); } @Bean ReactorDopplerClient dopplerClient(ConnectionContext connectionContext, TokenProvider tokenProvider) { return ReactorDopplerClient.builder() .connectionContext(connectionContext) .tokenProvider(tokenProvider) .build(); } @Bean ReactorUaaClient uaaClient(ConnectionContext connectionContext, TokenProvider tokenProvider) { return ReactorUaaClient.builder() .connectionContext(connectionContext) .tokenProvider(tokenProvider) .build(); }
CloudFoundryOperations BuilderThe CloudFoundryClient, DopplerClient, and UaaClients provide direct access to the raw REST APIs. This level of abstraction provides the most detailed and powerful access to the Cloud Foundry instance, but also requires users to perform quite a lot of orchestration on their own. Most users will instead want to work at the CloudFoundryOperations layer. Once again this is only an interface and the default implementation of this is the DefaultCloudFoundryOperations. To instantiate one, you configure it with a builder:
NOTE: The DefaultCloudfoundryOperations type does not require all clients in order to run. Since not all operations touch all kinds of clients, you can selectively configure the minimum needed. If a client is missing, the first invocation of a method that requires that client will return an error.
DefaultCloudFoundryOperations.builder() .cloudFoundryClient(cloudFoundryClient) .dopplerClient(dopplerClient) .uaaClient(uaaClient) .organization("example-organization") .space("example-space") .build();
In Spring-based applications, you'll want to encapsulate this in a bean definition as well:
@Bean DefaultCloudFoundryOperations cloudFoundryOperations(CloudFoundryClient cloudFoundryClient, DopplerClient dopplerClient, UaaClient uaaClient, @Value("${cf.organization}") String organization, @Value("${cf.space}") String space) { return DefaultCloudFoundryOperations.builder() .cloudFoundryClient(cloudFoundryClient) .dopplerClient(dopplerClient) .uaaClient(uaaClient) .organization(organization) .space(space) .build(); }
CloudFoundryOperations APIsOnce you've got a reference to the CloudFoundryOperations, it's time to start making calls to the Cloud Foundry instance. One of the simplest possible operations is list all of the organizations the user is a member of. The following example does three things:
System.outcloudFoundryOperations.organizations() .list() .map(OrganizationSummary::getName) .subscribe(System.out::println);
To relate the example to the description above the following happens:
.list() – Lists the Cloud Foundry organizations as a Flux of elements of type Organization..map(...) – Maps each organization to its name (type String). This example uses a method reference; the equivalent lambda would look like organizationSummary -> organizationSummary.getName().subscribe... – The terminal operation that receives each name in the Flux. Again, this example uses a method reference and the equivalent lambda would look like name -> System.out.println(name).CloudFoundryClient APIsAs mentioned earlier, the cloudfoundry-operations implementation builds upon the cloudfoundry-client API. That implementation takes advantage of the same reactive style in the lower-level API. The implementation of the Organizations.list() method (which was demonstrated above) looks like the following (roughly):
cloudFoundryClient.organizations() .list(ListOrganizationsRequest.builder() .page(1) .build()) .flatMapIterable(ListOrganizationsResponse::getResources) .map(resource -> OrganizationSummary.builder() .id(resource.getMetadata().getId()) .name(resource.getEntity().getName()) .build());
The above example is more complicated:
.list(...) – Retrieves the first page of Cloud Foundry organizations..flatMapIterable(...) – Substitutes the original Mono with a Flux of the Resources returned by the requested page..map(...) – Maps the Resource to an OrganizationSummary type.If you are having issues with the cf-java-client in your applications...
First, read this article on debugging reactive applications and watch this Spring Tips Video also on debugging reactive apps.
Beyond that, it is helpful to capture the following information:
cloudfoundry-client to DEBUG. For example with Spring Boot, set logging.level.cloudfoundry-client=debug.cloudfoundry-client.wire to TRACE. For example with Spring Boot, set logging.level.cloudfoundry-client.wire=trace.If you open a Github issue with a request for help, please include as much of the information above as possible and do not forget to sanitize any request/response data posted.
The project depends on Java 8. To build from source and install to your local Maven cache, run the following:
$ git submodule update --init --recursive $ ./mvnw clean install
It also depends on Immutables and won't compile in IDEs like Eclipse or IntelliJ unless you also have an enabled annotation processor. See this guide for instructions on how to configure your IDE.
To run the integration tests, run the following:
$ ./mvnw -Pintegration-test clean testTo run a specific integration test, run the following replacing with -Dtest=org.cloudfoundry.TestClass#test-method (#test-method is optional):
./mvnw -Pintegration-test clean test -Dtest=org.cloudfoundry.client.v3.ServiceBrokersTest#updateTo run tests & enable HTTP trace output, execute:
CLIENT_LOGGING_LEVEL=trace ./mvnw -Pintegration-test clean testIMPORTANT Integration tests require admin access and should be run against an empty Cloud Foundry instance. The integration tests are destructive, affecting nearly everything on an instance given the chance.
The integration tests require a running instance of Cloud Foundry to test against. To configure the integration tests with the appropriate connection information use the following environment variables:
| Name | Description |
|---|---|
TEST_ADMIN_CLIENTID |
Client ID for a client with permissions for a Client Credentials grant |
TEST_ADMIN_CLIENTSECRET |
Client secret for a client with permissions for a Client Credentials grant |
TEST_ADMIN_PASSWORD |
Password for a user with admin permissions |
TEST_ADMIN_USERNAME |
Username for a user with admin permissions |
TEST_APIHOST |
The host of a Cloud Foundry instance. Typically something like api.local.pcfdev.io. |
TEST_PROXY_HOST |
(Optional) The host of a proxy to route all requests through |
TEST_PROXY_PASSWORD |
(Optional) The password for a proxy to route all requests through |
TEST_PROXY_PORT |
(Optional) The port of a proxy to route all requests through. Defaults to 8080. |
TEST_PROXY_USERNAME |
(Optional) The username for a proxy to route all requests through |
TEST_SKIPSSLVALIDATION |
(Optional) Whether to skip SSL validation when connecting to the Cloud Foundry instance. Defaults to false. |
UAA_API_REQUEST_LIMIT |
(Optional) If your UAA server does rate limiting and returns 429 errors, set this variable to the smallest limit configured there. Whether your server limits UAA calls is shown in the log, together with the location of the configuration file on the server. Defaults to 0 (no limit). |
TEST_FAIL_ON_UNKNOWN_PROPERTIES |
(Optional) If "true", unknown values received from CF result in a parsing error. This usually happens when client and server versions do not match. When "false", unknown properties will be ignored allowing the execution of integration-tests. Use with care! Defaults to true. |
SKIP_BROWSER_AUTH_TESTS |
(Optional) Set to true to skip integration tests that require browser-based authentication (e.g., SSO tests). Useful when the Cloud Foundry instance's UAA does not have browser-based authentication configured. Defaults to false. |
SKIP_METRIC_REGISTRAR_TESTS |
(Optional) Set to true to skip integration tests that require the Metric Registrar service (e.g., MetricRegistrarTest). Useful when the Cloud Foundry instance does not have the Metric Registrar service available. Defaults to false. |
SKIP_TCP_ROUTING_TESTS |
(Optional) Set to true to skip TCP routing integration tests (TcpRoutesTest, RouterGroupsTest). Useful when the Cloud Foundry instance does not have TCP routing configured (i.e., no routing_endpoint in the info payload). Defaults to false. |
TEST_QUOTAS_ROUTES_RESERVED_PORTS |
(Optional) When set to a positive integer, sets reserved TCP route ports (total_reserved_ports) on the default organization quota to that value during integration test bootstrap. When set to -1, sets the reserved ports to unlimited. Use this when the platform leaves that limit at 0 on the default quota but you still run TCP routing tests (SKIP_TCP_ROUTING_TESTS unset or false). If unset, no quota change is applied. Maps to the Spring property test.quotas.routes.reserved-ports. |
SKIP_V2_TESTS |
(Optional) Set to true to skip all V2 API integration tests. Useful when the Cloud Foundry V2 API is rate-limited or unavailable. When enabled, tests annotated with @RequiresV2Api will be skipped, including V3 tests that depend on V2 API calls (e.g., service broker creation). Defaults to false. |
If you do not have access to a CloudFoundry instance with admin access, you can run one locally using bosh-deployment & cf-deployment and Virtualbox.
For instructions installing Bosh in VirtualBox using bosh-deployment, see the Install Section to install Bosh.
With Bosh installed, follow the deployment guide to get CF installed. You can skip to step 4, since you're installing into VirtualBox. Be sure to read the entire document before you begin, however pay specific attention to this section which has specific instructions for running locally.
Lastly before running the tests, it is strongly recommended that you take a snapshot of the VMs in the environment. This allows for the quick rollback of the environment should the tests break something (they don't generally, integration tests should clean up after themselves).
Pull requests and Issues are welcome.
This project is released under version 2.0 of the Apache License.
cloudfoundry/cf-java-client is a public repo on GitHub by cloudfoundry. Java Client Library for Cloud Foundry.
It declares the Apache-2.0 license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-17. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Reverse engineer anything with agents, from app behavior down to native binaries.
hsweb (haʊs wɛb) 是一个基于spring-boot 2.x开发 ,首个使用全响应式编程的企业级后台管理系统基础项目。


Practical Project Reactor and reactive programing workshop
Cloud Foundry BOSH is an open source tool chain for release engineering, deployment and lifecycle management of large scale distributed services.

The canonical open source deployment manifest for Cloud Foundry

Stratos: Web-based Management UI for Cloud Foundry and Kubernetes