ci(e2e): fix heredoc indentation in user-data script#489
Merged
Conversation
YAML `run: |` strips 10 spaces of indentation. The `sed`-based heredoc placed the closing USERDATA delimiter at 12 spaces (→ 2 spaces after stripping), but bash `<<` requires it at column 0. Switch to `cat >` with content at 10-space YAML indent so the heredoc body and delimiter land at column 0 after YAML processing.
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
1 participant
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
run: |strips 10 spaces of indentation; thesed-based heredoc placed the closingUSERDATAdelimiter at 12 spaces (→ 2 spaces after stripping), but bash<<requires it at column 0sed 's/^ //'tocat >with content at 10-space YAML indent so the heredoc body and delimiter land at column 0 after YAML processingFixes: https://github.com/boxlite-ai/boxlite/actions/runs/25384002678/job/74439883200
Test plan
syntax error: unexpected end of file/tmp/user-data.shscript content is correct (no leading whitespace in script body)