cloudfoundry / cloudfoundry/cf-java-client
CAPI V2 EOL
@Kehrlann 已经在做这个了。
开始于 2025年12月5日。
- 主要语言
- Java
- 星标
- 334
- 派生
- 319
- PR 合并指标
- 30 天内没有已合并 PR
描述
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:
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。