Fix Multiline Output

[theturtle32]

It is undocumented functionality, but this actions workflow does also expose the result of the helm command execution as an output called helm_output. Unfortunately, because a lot of unnecessary character escaping is done for newlines, carriage returns, and the percent symbol, the result is fairly difficult to use.

The Github Actions Docs specifies that you can use the same multi-line output format for outputs as you can for environment variables, so no special tricks are required. The approach is based on the same standard heredoc method you would use in a shell script.

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#setting-an-output-parameter

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#multiline-strings

Important

This pull request does also include a further enhancement which splits helm's NOTES.txt output from the rest of the output, and populates separate Github Actions outputs for each. This makes it easier to render the NOTES.txt into the Markdown-formatted workflow summary.

The two outputs are:

• helm_output – Everything that was output by the helm command before the line NOTES:
• helm_notes – Everything that was output by the helm command after the line NOTES:

Please let me know if you want a clean pull request that does not make both of these changes at once.
***Update: this has been extracted into a separate PR. #92 ***

[WyriHaximus]

It is undocumented functionality, but this actions workflow does also expose the result of the helm command execution as an output called helm_output. Unfortunately, because a lot of unnecessary character escaping is done for newlines, carriage returns, and the percent symbol, the result is fairly difficult to use.

The Github Actions Docs specifies that you can use the same multi-line output format for outputs as you can for environment variables, so no special tricks are required. The approach is based on the same standard heredoc method you would use in a shell script.

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#setting-an-output-parameter

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#multiline-strings

Somehow I forgot to update this one, thanks for doing that 👍 . It does need documenting tho, but I like both propose changes.

Important

This pull request does also include a further enhancement which splits helm's NOTES.txt output from the rest of the output, and populates separate Github Actions outputs for each. This makes it easier to render the NOTES.txt into the Markdown-formatted workflow summary.

The two outputs are:

• helm_output – Everything that was output by the helm command before the line NOTES:
• helm_notes – Everything that was output by the helm command after the line NOTES:

Please let me know if you want a clean pull request that does not make both of these changes at once.

IMHO splitting it up makes most sense, all 3 commits of the original PR are welcome as PR's.

[WyriHaximus]

Thanks for splitting up the PR and doing all this work 👍

[theturtle32]

Thanks for splitting up the PR and doing all this work 👍

You're welcome!