Skip to content

Clarify open source and commercial EOL of v2 endpoints #586

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

Open
mjj209 wants to merge 1 commit into
base: tcf-102
Choose a base branch
from
Open

Clarify open source and commercial EOL of v2 endpoints #586

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 5 additions & 0 deletions capi/client-libraries.html.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,11 @@ platform. You can use it to manage orgs, spaces, and apps, which includes user r

<%= vars.capi_link %>

### CAPI v2 Deprecation and End of Life
CAPI v2 endpoints are deprecated in both Open Source Cloud Foundry since 2021 and <%= vars.app_runtime_abbr %> in version 6.0 and forward. Given these endpoints are deprecated, new development should use the v3 endpoints.
Open Source Cloud Foundry has plans to end of life the v2 endpoints following this RFC: https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0032-cfapiv2-eol.md
<%= vars.app_runtime_abbr %> does not have plans to end of life the V2 endpoints in the current LTS releases.

## <a id='client-libraries'></a>Client libraries

While you can develop apps that use CAPI by calling it directly as in the API documentation, you might want to use an existing client library. See the following available client libraries.
Expand Down