[main] Fix pipeline when USE_LATEST_CAPI=true is used#3714
Merged
anujc25 merged 1 commit intocloudfoundry:mainfrom Feb 11, 2026
Merged
[main] Fix pipeline when USE_LATEST_CAPI=true is used#3714anujc25 merged 1 commit intocloudfoundry:mainfrom
USE_LATEST_CAPI=true is used#3714anujc25 merged 1 commit intocloudfoundry:mainfrom
Conversation
- Remove stemcell field from CAPI release in use-latest-capi.yml ops file - Remove unused jumpbox private key extraction in create-bosh-lite workflow These changes resolve deployment issues when using the latest CAPI release by ensuring the ops file properly removes conflicting release metadata.
USE_LATEST_CAPI=trueUSE_LATEST_CAPI=true is used
Gerg
approved these changes
Feb 11, 2026
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
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.
Description of the Change
Fix pipeline when USE_LATEST_CAPI=true is used
These changes resolve deployment issues when using the latest CAPI release
by ensuring the ops file properly removes conflicting release metadata.
Why Is This PR Valuable?
Fixes the bosh lite env creation pipeline.
Applicable Issues
How Urgent Is The Change?
Urgent to unblock some of the PRs that depend on the latest CAPI.
Other Relevant Parties
None