[steps] [ENG-14373] Fix multiline slack messages with env vars #478
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.
Why
expo/eas-cli#2728
When setting an env var to a multiline string and then passing it as the context of a Slack message to the
eas/send_slack_message
function the new-line characters are not correctly handled. The implicit new-lines are removed, while explicit\n
characters are used as\
andn
.How
Updated the
set-env
bash script to preserve the implicit new-lines when saving the var value to the file.Added a util function that fixes the explicit escape characters when reading the raw env value from the file and updating the context.
Test Plan
Manual tests
Config
Before
After