Skip to content
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.

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

Detect CF-on-K8s in cf api #1

Merged
merged 1 commit into from
Oct 4, 2021
Merged

Detect CF-on-K8s in cf api #1

merged 1 commit into from
Oct 4, 2021

Conversation

gcapizzi
Copy link

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

Copy link
Collaborator

@jdgonzaleza jdgonzaleza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
cc: @dominicrobertsc

Makefile Outdated Show resolved Hide resolved
@gcapizzi gcapizzi requested review from dominicrobertsc and removed request for a-b October 4, 2021 10:21
@gcapizzi
Copy link
Author

gcapizzi commented Oct 4, 2021

Thanks @jdgonzaleza! I have added @dominicrobertsc as a second reviewer.

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 danail-branekov merged commit 3584a3b into master Oct 4, 2021
@danail-branekov danail-branekov deleted the wip-cf-api branch October 4, 2021 15:30
matt-royal pushed a commit that referenced this pull request Mar 1, 2023
Upgrades go from 1.18 to 1.19

Co-authored-by: Juan Diego Gonzalez <gojuan@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants