Confusing messaging when using `command` on ssh executor

[alangrafu]

Using ssh executor

    command: |
      cd /root/ && \
      curl --retry 5 -m 10  https://XYZ && \
      ./command analyze && \
      curl --retry 5 -m 10  https://XYZ

fails, but

    command: |
      cd /root/ && curl --retry 5 -m 10  XYZ && ./command analyze && curl --retry 5 -m 10  https://XYZ

works fine. I got an error saying use command instead of script, but that is what I did.

[kriyanshii]

use it as

steps:
  - name: remote-script
    executor:
      type: ssh
      config:
        user: admin
        host: backup.server.com
        key: ${SSH_KEY_PATH}
    script: |
      #!/bin/bash
      set -e
      
      echo "Starting backup..."
      tar -czf /backup/app-$(date +%Y%m%d).tar.gz /var/www
      
      echo "Cleaning old backups..."
      find /backup -name "app-*.tar.gz" -mtime +7 -delete
      
      echo "Backup complete

[alangrafu]

thanks but the error message explicitly says do not use script. I guess I need to update to check this doesn't happen in the very latest version

[kriyanshii]

can you please share stderr?

[alangrafu]

The issue is not shown in stderr, since I can't save a dag like this

[yottahmd]

I'm afraid the ssh executor does not support script field at the moment.

[kriyanshii]

Using ssh executor

    command: |
      cd /root/ && \
      curl --retry 5 -m 10  https://XYZ && \
      ./command analyze && \
      curl --retry 5 -m 10  https://XYZ

fails, but

    command: |
      cd /root/ && curl --retry 5 -m 10  XYZ && ./command analyze && curl --retry 5 -m 10  https://XYZ

works fine. I got an error saying use command instead of script, but that is what I did.

What you did last maybe the way to go right now!

[alangrafu]

Yeah, it is not such a big deal, but the error is super confusing.

BTW I updated to 1.23.0 and tried #1374 (comment) without success

[ghansham]

Can you try removing pipe operator and give a try with and without line continuation \