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 cloudfoundry/community#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 Migrate Operations to use V3 API #1325
• route service binding support, see Add v3 organization quotas and service keys APIs #1168 (comment)
• delete user request support v3/user endpoint not covered #1294
• v2/info call getting triggered internally while creating CloudFoundryClient and consuming v3 api's v2/info call getting triggered internally while creating CloudFoundryClient and consuming v3 api's #1229

issues tracking implemented V3 features that should be closed:

• Add support for /v3/apps/:guid/actions/apply_manifest #999
• Missing V3 Service Plan Visibility #1077