You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the command locally, scp authenticates without asking a password.
But when the publishing action is kicked of via goreleaser, it asks for a password.
I tried specifying an identity like above, but still I am asked for a password.
Just after writing above question, I decided to give it one more go and I added an env var like this:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I have been investigating an issue that I encounter when using a bespoke publisher using scp.
My publisher looks like this:
When running the command locally, scp authenticates without asking a password.
But when the publishing action is kicked of via goreleaser, it asks for a password.
I tried specifying an identity like above, but still I am asked for a password.
Just after writing above question, I decided to give it one more go and I added an env var like this:
This did the trick :-)
I thought that it would be good to still add this to the Q&A if somebody would run into the same situation.
Beta Was this translation helpful? Give feedback.
All reactions