-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Description
Dear colleagues,
I am not sure why, but latest seems to be a step backwards (2025 -> 2020):
>docker run -it docker.wdf.sap.corp:50000/ppiper/cf-cli:latest sh
$ cf -v
cf version 6.53.0+8e2b70a4a.2020-10-01
>docker run -it docker.wdf.sap.corp:50000/ppiper/cf-cli:v22 sh
$ cf -v
cf version 8.14.1+2bcb856.2025-06-10
This is NOT an issue (not really) while using "cf login" as it is still using CF CLI v3. But while using "cf auth" it's falling back to CF CLI v2:
>docker run -it docker.wdf.sap.corp:50000/ppiper/cf-cli:latest sh
$ cf login -a https://api.cf.sap.hana.ondemand.com -u [email protected] -p abc --skip-ssl-validation
API endpoint: https://api.cf.sap.hana.ondemand.com
[...]
API endpoint: https://api.cf.sap.hana.ondemand.com (API version: 3.203.0)
>docker run -it docker.wdf.sap.corp:50000/ppiper/cf-cli:latest sh
$ cf api api.cf.sap.hana.ondemand.com --skip-ssl-validation
Setting api endpoint to api.cf.sap.hana.ondemand.com...
OK
$ cf auth [email protected] abc
Cloud Foundry API version 2.268.0 requires CLI version 8.0.0. You are currently on version 6.53.0+8e2b70a4a.2020-10-01. To upgrade your CLI, please visit: https://github.com/cloudfoundry/cli#downloads
For testing "cf login" vs. "cf auth" please use a new docker instance! When you perform "cf login" in same instance first, "cf auth" will run on CF CLI v3 as well.
For my environment, I cannot use "cf login" as I need to build spaces etc. first (which are required for "cf login" but not for "cf auth").
Thx & BR,
Andreas
Metadata
Metadata
Assignees
Labels
No labels