sh in vars is inconsistently chomping linebreaks compared to cmds?

[fj]

I'd like to write this:

vars:
  ASSETS_SYNC_SESSION_KEY:
    sh:
      >
        AWS_SECRET_ACCESS_KEY={{.AWS_SECRET_ACCESS_KEY}} \
        AWS_ACCESS_KEY_ID={{.AWS_ACCESS_KEY_ID}} \
        aws sts get-session-token

but instead I get:

" AWS_ACCESS_KEY_ID=not-implemented": executable file not found in $PATH
task: Command "AWS_SECRET_ACCESS_KEY=not-implemented \ AWS_ACCESS_KEY_ID=not-implemented \ aws sts get-session-token
" failed: exit status 127
# fails, treated as one line with no line breaks

This seems to happen because the parsing of sh: is deleting the linebreaks. I expected that the multiline YAML here would work the same way as it does with cmds -- this works, for example:

tasks:
  example:
    cmds:
      - >
        AWS_SECRET_ACCESS_KEY={{.AWS_SECRET_ACCESS_KEY}} \
        AWS_ACCESS_KEY_ID={{.AWS_ACCESS_KEY_ID}} \
        aws sts get-session-token
        # above works as expected, treated as three lines

Is this a bug or is this the expected behavior?

[ghostsquad]

The use of > replaces newlines with spaces according to the yaml spec.

Try using | or |- instead.

https://yaml-multiline.info/

Also note the difference in indenting between your first and second examples. First example it's indented 2 spaces more under the >.

And the fact that in the first example, you aren't putting the > on the same line as the key like you are in the second example (it's inline with the - which is the start of the list item)

[fj]

You're right! Thanks for catching that.

[ghostsquad]

You're right! Thanks for catching that.

Please mark as answered to help other users.