-
Notifications
You must be signed in to change notification settings - Fork 29
cf target https://api.cloudfoundry.com error #1
Comments
Hi. The "cf" client is only for V2 targets. You should use the "vmc" client
On Saturday, March 30, 2013, wangzifeng wrote:
Tim Lang |
If |
Vmc is still the correct client to use with the v1 Cloud Foundry server On Wednesday, April 3, 2013, Eli wrote:
Tim Lang |
I was instructed as well, via a core partner's docs to use |
Agreed, the documentation is confusing and will be updated to correctly refer to vmc / cf. |
How do I create a v2 DNS target? |
@Swps can you give a little more explanation on what you're trying to achieve? I don't think I understand what exactly you want to know. Thanks |
@dmrschmidt he's asking how to create a target compatible with |
But the document of cloudfoundry show me 'cf target https://api.cloudfoundry.com', it's worry? |
Hi. Not sure I understand the question but a few points of clarification:
Not sure if that helps?
On Fri, May 3, 2013 at 12:06 AM, shffdc notifications@github.com wrote:
|
To add to @tlang's answer, the docs.cloudfoundry.com site clearly states that at the moment we are in a period of transition between v1 and v2. The docs are written for version 2, but there's a link to the older docs. As of today (May 3) our public api.cloudfoundry.com endpoint is at v1, so you should use the vmc tool to target it. If you download the Open Source components and deploy your own Cloud Foundry instance to your choice of infrastructure you can get a v2 version and use the cf tool. |
when run:
cf target https://api.cloudfoundry.com
returns:
V1 targets are no longer supported.
Not able to use login feature of CF
The text was updated successfully, but these errors were encountered: