feat: capture stdout and store as output

[GammaGames]

Possibly fixes #274, #38

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - name: SSH
        id: ssh
        uses: https://github.com/GammaGames/ssh-action@master
        with:
          host: [fill in]
          capture_stdout: 'true'
          script: |
            ls -l ~/test/
      - name: echo
        run: echo "${{ steps.ssh.outputs.stdout }}"

If successful, it has the following in steps.ssh.outputs.stdout:

======CMD======
ls -l ~/test/
======END======
out: total 0
out: -rw-rw-r-- 1 user group 0 Jan  2 14:24 file1
out: -rw-rw-r-- 1 user group 0 Jan  2 14:24 file2
==============================================
✅ Successfully executed commands to all host.
==============================================

On error it acts like it does now.

[GammaGames]

One potential issue is that secrets aren't masked in the output variable like they are in the log. I was able to fix it with a filtering step, but it's manual:

- uses: mad9000/actions-find-and-replace-string@4
  id: filter
  with:
    source: ${{ steps.ssh.outputs.stdout }}
    find: '${{ secrets.value }}'
    replace: '***'
    replaceAll: true
- run: echo '${{ steps.filter.outputs.value }}'

[GammaGames]

fixed conflicts

edit: fixed conflicts

[hasechris]

@appleboy
Could you take a look at this? Having an output would be great

[Digital-Lemon]

I'd add a variable to enable (or disable) this behavior, as sometimes the outputs could be huge

[GammaGames]

Good point, it should probably also not capture by default because the output has all command output (without censoring, like the gh step interface has)

[uchar]

I think the script should handle masking secrets by itself , not very good practice to depend on another step for doing it , this can cause security issues if some one forget it

[GammaGames]

I agree! Is there a way to get secret names at runtime? I was under the impression that github action output is filtered before displaying, but doesn't have any filtering on the server side
Edit: "censoring" values should probably be another pr, maybe another variable you could pass ${{ toJSON(secrets) }} to?

[mikesalvia]

@GammaGames or @appleboy is there any update on when this would be merged in?

[GammaGames]

@mikesalvia I don't know, but I should probably make it optional and disabled by default first. I started working on that a little today but have yet to test it: https://github.com/GammaGames/ssh-action/tree/capture_vars

[GammaGames]

Okay it's optional now. Idk why it's not showing in the github action, it's working fine on nektos act and gitea: https://github.com/GammaGames/ssh-action/actions/runs/12017938366/job/33504424638

edit: started discussion asking for help - https://github.com/orgs/community/discussions/145592

[appleboy]

I will take it.

[appleboy]

@GammaGames Please help to resolve the conflicts.

[GammaGames]

Fixed, also changed the test to use true instead of "true" (though both work)

Why remove the script_stop feature?

[appleboy]

@GammaGames Thanks.

Why remove the script_stop feature?

The script_stop function detects each line of instruction, but it cannot handle line breaks using the backslash (). Therefore, I will write another method to solve this problem.

[banagale]

Thank you @GammaGames and all who assisted!