cloudfoundry / cloudfoundry/cf-java-client
CAPI V2 EOL
@Kehrlann is already working on this.
Since Dec 5, 2025.
- Dominant language
- Java
- Stars
- 334
- Forks
- 319
- PR merge metrics
- No merged PRs in 30d
Description
Thanks for all contributions to use CAPI V3 in the past years.
Phase 2 mention of RFC0032 - CF API v2 End of Life mentions the following and is tracked into https://github.com/cloudfoundry/community/issues/1001
Phase 2 (after Checkpoint 1, ~mid/end 2025)
- Engineering work so that all CFF-controlled clients use v3 by default
CF API client libraries like cf-java-client, cf-goclient [...] should plan for closing gaps in CF API v3 support and for removing their CF API v2 implementation.
This is an issue that tracks V2 feature parity, and V2 removal (sorry if I missed an existing one)
Cf-java client v2 feature parity:
- migrating Operations classes to V3, tracked in #1325
- route service binding support, see https://github.com/cloudfoundry/cf-java-client/issues/1168#issuecomment-3512737099
- delete user request support https://github.com/cloudfoundry/cf-java-client/issues/1294
- v2/info call getting triggered internally while creating CloudFoundryClient and consuming v3 api's #1229
issues tracking implemented V3 features that should be closed:
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.