-
-
Notifications
You must be signed in to change notification settings - Fork 563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture stdout and store as output #287
base: master
Are you sure you want to change the base?
Conversation
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 }}' |
edit: fixed conflicts |
@appleboy |
I'd add a variable to enable (or disable) this behavior, as sometimes the outputs could be huge |
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) |
Possibly fixes #274, #38
If successful, it has the following in
steps.ssh.outputs.stdout
:On error it acts like it does now.