Fix CF CLI v8 compatibility issues in CloudFoundry setup#118
Merged
Conversation
ramonskie
approved these changes
Nov 25, 2025
Contributor
ramonskie
left a comment
ramonskie
left a comment
There was a problem hiding this comment.
lgtm but squash commits
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes three compatibility issues preventing switchblade from working with CF CLI v8 and modern Cloud Foundry deployments that have CF API v2 disabled.
Problems Fixed
bind-security-groupcommand syntax (Line 280) - CF CLI v8 requires the--spaceflag instead of positional space argument. Changed frombind-security-group <sg> <org> <space>tobind-security-group <sg> <org> --space <space>Security groups API endpoint (Lines 291-312) - Migrated from
/v2/security_groupsto/v3/security_groupswith updated JSON structure. Used flat JSON structure in v3 -resources[].nameinstead ofresources[].entity.namemap-routeflag removal (Line 360) - CF CLI v8 removed the--random-portflag for TCP routes - this behaviour is now the default for TCP routesTesting
Tested against Cloud Foundry deployment with: