Re: Announcement: CC API v2 Deprecation Plan
Mike Lloyd <mike@...>
Recently I had a use case to use CAPI for exporting some app information, and I struggled a bit here and there to both find a client as well as build one myself for v2. I think what could be really interesting, and thinking out loud, would be an OpenAPI 3.0 definition for v3. I think that would really help client maintainers (maybe now but definitely in the future) make the migration a bit easier for multi-language projects. I briefly looked to see if an API spec existed, but I didn't see anything.
Looking forward, having an API spec for CAPI would be very helpful even past the migration, then clients can be very easily constructed in any language.
Professional Member, ACM
From: cf-dev@... <cf-dev@...> on behalf of Guillaume Berche via Lists.Cloudfoundry.Org <bercheg=gmail.com@...>
Sent: Tuesday, March 5, 2019 10:13 AM
Subject: Re: [cf-dev] Announcement: CC API v2 Deprecation Plan
I'd like to renew related feedback provided last october on the subject at https://lists.cloudfoundry.org/g/cf-dev/topic/26659245#8303
There are many tooling out there that currently rely on the CC API V2 (such as UIs, service brokers, provisionning tools such as terraform-provider-cf or SAP MTA...). These tooling usually leverage CC API clients . Ways to reduce impacts for such tooling would be to work with client maintainers (both official, experimental and unsupported) to sync the CC API V2 deprecation with availability of CC API V3 support in clients from most widely used programming languages.
In particular, regarding the go-lang client, we had a related exchange with the CLI team at cf summit, and a related issue https://github.com/cloudfoundry/cli/issues/1481 tracks this feedback, which seems to have received positive community interest. It would be useful to hear feedback from the CLI or VAT teams on this suggestion.
On Wed, Feb 13, 2019 at 11:34 PM Greg Cobb <gcobb@...> wrote: