[main] Fix bbl print-env producing output in wrong format#3699
Merged
anujc25 merged 1 commit intocloudfoundry:mainfrom Feb 4, 2026
Merged
[main] Fix bbl print-env producing output in wrong format#3699anujc25 merged 1 commit intocloudfoundry:mainfrom
anujc25 merged 1 commit intocloudfoundry:mainfrom
Conversation
As a workaround, force the output in posix format using the --shell-type argument. Partially-fixes: cloudfoundry#3698
anujc25
changed the title
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.
As a workaround, force the output in posix format using the --shell-type argument.
Partially-fixes: #3698
Note: Please create separate PR for every branch (main and v8) as needed.
Description of the Change
Integration tests are broken because bbl's output of the bbl state is in the format for the wrong shell.
I will continue to find the root cause for the regression, but in the meantime this is a workaround to unblock setup/cleaning of bosh-lite environments.
Why Is This PR Valuable?
Fixes CI
Applicable Issues
How Urgent Is The Change?
Since CI is broken, this is time sensitive
Other Relevant Parties
Who else is affected by the change?