This repository has been archived by the owner on Nov 3, 2021. It is now read-only.
[Feature]: Developer can target a cf-k8s foundation via cf api
#10
Assignees
Labels
Comments
cf can be pointed to a cf-k8s foundation via cf apicf can be pointed to a cf-k8s foundation via cf api and cf login
cf can be pointed to a cf-k8s foundation via cf api and cf logincf can be pointed to a cf-k8s foundation via cf api
cf can be pointed to a cf-k8s foundation via cf apicf CLI to a cf-k8s foundation via cf api
cf CLI to a cf-k8s foundation via cf apicf-k8s foundation via cf api
gcapizzi
added a commit
to eirini-forks/cli
that referenced
this issue
Sep 23, 2021
This makes `cf api` able to detect the `cf-on-k8s` flag in the root endpoint response and persist this information in the config. This will allow us to enable CF-on-K8s-specific behaviour for every following command. Issue: cloudfoundry/cf-k8s-api#10 Co-authored-by: Danail Branekov <danailster@gmail.com>
This was referenced Sep 23, 2021
danail-branekov
added a commit
to eirini-forks/cli
that referenced
this issue
Sep 24, 2021
This makes `cf api` able to detect the `cf-on-k8s` flag in the root endpoint response and persist this information in the config. This will allow us to enable CF-on-K8s-specific behaviour for every following command. Issue: cloudfoundry/cf-k8s-api#10 Co-authored-by: Danail Branekov <danailster@gmail.com> Co-authored-by: Giuseppe Capizzi <gcapizzi@pivotal.io>
danail-branekov
added a commit
that referenced
this issue
Sep 24, 2021
Also introduce root response presenter and response type Issue: #10 Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
Birdrock
pushed a commit
that referenced
this issue
Sep 29, 2021
Also introduce root response presenter and response type Issue: #10 Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
danail-branekov
added a commit
to eirini-forks/cli
that referenced
this issue
Sep 30, 2021
This makes `cf api` able to detect the `cf-on-k8s` flag in the root endpoint response and persist this information in the config. This will allow us to enable CF-on-K8s-specific behaviour for every following command. We have introduced a new `selfcontained` integration suite which contains tests that do not need to be run against a cf deployment. Issue: cloudfoundry/cf-k8s-api#10 Co-authored-by: Danail Branekov <danailster@gmail.com> Co-authored-by: Giuseppe Capizzi <gcapizzi@pivotal.io> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
danail-branekov
added a commit
to eirini-forks/cli
that referenced
this issue
Oct 4, 2021
This makes `cf api` able to detect the `cf-on-k8s` flag in the root endpoint response and persist this information in the config. This will allow us to enable CF-on-K8s-specific behaviour for every following command. We have introduced a new `selfcontained` integration suite which contains tests that do not need to be run against a cf deployment. Issue: cloudfoundry/cf-k8s-api#10 Co-authored-by: Danail Branekov <danailster@gmail.com> Co-authored-by: Giuseppe Capizzi <gcapizzi@pivotal.io> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
danail-branekov
added a commit
to eirini-forks/cli
that referenced
this issue
Oct 7, 2021
This makes `cf api` able to detect the `cf-on-k8s` flag in the root endpoint response and persist this information in the config. This will allow us to enable CF-on-K8s-specific behaviour for every following command. We have introduced a new `selfcontained` integration suite which contains tests that do not need to be run against a cf deployment. Issue: cloudfoundry/cf-k8s-api#10 Co-authored-by: Danail Branekov <danailster@gmail.com> Co-authored-by: Giuseppe Capizzi <gcapizzi@pivotal.io> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
gcapizzi
added a commit
to eirini-forks/cli
that referenced
this issue
Oct 14, 2021
This makes `cf api` able to detect the `cf-on-k8s` flag in the root endpoint response and persist this information in the config. This will allow us to enable CF-on-K8s-specific behaviour for every following command. We have introduced a new `selfcontained` integration suite which contains tests that do not need to be run against a cf deployment. Issue: cloudfoundry/cf-k8s-api#10 Co-authored-by: Danail Branekov <danailster@gmail.com> Co-authored-by: Giuseppe Capizzi <gcapizzi@pivotal.io> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Our strategy for authenticating the
cfCLI is to teach the CLI to understand and apply$KUBECONFIGwhen talking tocf-k8sfoundations.Here we want to extend the
cfCLI to be able to recognise acf-k8sfoundation when pointed at it viacf api.Acceptance
After running
cf apiagainst acf-k8sAPI, I should see something like this in$CF_HOME/config.json:If I run
cf apiagainst a traditional CF API after that, I should see this:Dev notes
cf apiwill interrogate the root endpoint of the CF API to gather information about the foundation: we want to leverage this to let the CLI know that this is acf-k8sfoundation and provide the necessary information it needs to work.The text was updated successfully, but these errors were encountered: