We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I use script_stop: true the output of the cat command becomes
script_stop: true
{ "RESTORE_BACKUP": "$RESTORE_BACKUP", "FTP_HOST": "$FTP_HOST", DRONE_SSH_PREV_COMMAND_EXIT_CODE=0 ; if [ 0 -ne 0 ]; then exit 0; fi; { DRONE_SSH_PREV_COMMAND_EXIT_CODE=0 ; if [ 0 -ne 0 ]; then exit 0; fi;
- name: Clone project and run docker uses: appleboy/ssh-action@master env: FTP_HOST: ${{ secrets.FTP_HOST }} RESTORE_BACKUP: ${{ github.event.inputs.restoreBackup }} with: command_timeout: 60m script_stop: true host: ${{ secrets.SSH_HOST }} username: ${{ secrets.SSH_USER }} key: ${{ secrets.SSH_PRIVATE_KEY }} port: ${{ secrets.SSH_PORT }} envs: FTP_HOST,RESTORE_BACKUP script: | cat <<EOF > ./inputsData/deployEnvs.json { "RESTORE_BACKUP": "$RESTORE_BACKUP", "FTP_HOST": "$FTP_HOST", } EOF
it works fine without script_stop: true
The text was updated successfully, but these errors were encountered:
bumped into the same issue when using ssh-action to update nginx configs remotely
this bug makes HEREDOC unusable in this context :(
as a workaround I had to convert the HEREDOC into one-liner which greatly reduced the readability of the workflow
Sorry, something went wrong.
I can confirm that if statements are not working correctly with script_stop=true.
if
script_stop=true
Script:
echo "TMP TESTING IF" if [[ "2" == "1" ]]; then echo "True" else echo "False" fi
Output:
out: TMP TESTING IF 2024/09/24 21:19:30 Process exited with status 1
echo "TMP TESTING IF" if [[ "1" == "1" ]]; then echo "True" else echo "False" fi
out: TMP TESTING IF out: True 2024/09/24 21:20:40 Process exited with status 1
Update: disabling stop_script in autodeploy due to the known issue: a…
dabf07f
…ppleboy/ssh-action#335
I will disable the script_stop flag on the next version.
script_stop
appleboy
No branches or pull requests
Describe the bug
When I use
script_stop: true
the output of the cat command becomesYaml Config
it works fine without
script_stop: true
The text was updated successfully, but these errors were encountered: