Skip to content

TOC checkpoint 1 for rfc-0032-cfapiv2-eol #1058

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 4, 2025
Merged

TOC checkpoint 1 for rfc-0032-cfapiv2-eol #1058

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
589855d
TOC checkpoint 1 for rfc-0032-cfapiv2-eol
stephanme Jan 28, 2025
84ee4fe
Update PR number
stephanme Jan 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions toc/rfc/rfc-0032-cfapiv2-eol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,8 @@ If the TOC does not approve moving to the next phase, the TOC will decide a numb
- Turn off CF API v2 by default in cf-deployment (set CAPI property [cc.temporary_enable_v2](https://bosh.io/jobs/cloud_controller_ng?source=github.com/cloudfoundry/capi-release&version=1.185.0#p%3dcc.temporary_enable_v2) to false). Operators may still re-enable v2.

**Checkpoint 1**
- TOC approval
- [cf-deployment v47.0.0](https://github.com/cloudfoundry/cf-deployment/releases/tag/v47.0.0) ships with disabled CF API v2. It can be re-enabled by operators using [enable-v2-api.yml](https://github.com/cloudfoundry/cf-deployment/blob/main/operations/enable-v2-api.yml).
- TOC approval documented in PR [community#1058](https://github.com/cloudfoundry/community/pull/1058)

**Phase 2** (after Checkpoint 1, ~mid/end 2025)
- Engineering work so that all CFF-controlled clients use v3 by default
Expand All @@ -58,4 +59,4 @@ If the TOC does not approve moving to the next phase, the TOC will decide a numb
- Cloud Foundry users and operators may use tooling and CI/CD pipelines which still rely on CF API v2 and therefore have migration efforts.

CF API v2 specific rate limiting and the feature flag to disable CF API v2 completely is already implemented in CAPI.
The [CF API v3 Upgrade Guide](https://v3-apidocs.cloudfoundry.org/index.html#upgrade-guide) helps authors of CF api clients to migrate from v2 to v3.
The [CF API v3 Upgrade Guide](https://v3-apidocs.cloudfoundry.org/index.html#upgrade-guide) helps authors of CF api clients to migrate from v2 to v3.