Upgrade to switchblade v0.9.2 for CF API v3 compatibility #857
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.
What is this change?
This PR upgrades the nodejs-buildpack to use switchblade v0.9.2, which adds proper support for CF API v3 staging log capture.
Why was this change made?
When migrating to CF API v3, staging failure logs are no longer automatically captured in the logs buffer during test execution. Switchblade v0.9.2 addresses this by automatically fetching logs using
cf logs --recentwhen staging fails, which is essential for tests that verify buildpack error messages (like the override buildpack test).Changes included
Dependencies
Test Updates
override_test.go: Simplified log assertions and removed complex matchersContainLinesmatchersTooling
tools.sh: Check for existing CF CLI before attempting installationTesting
Integration tests pass locally using fly execute with BBL environment:
Related Work
This change follows the same pattern used in r-buildpack PR for CF API v3 migration.