The current bash script in entrypoint.sh doesn't cope with Base64 strings including new line characters. Unfortunately, these are often included by default when you pipe to base64.
Supplying a string with new lines causes this action to fail with base64: invalid input. I can replicate the problem locally with the following two lines:
The current bash script in
entrypoint.sh
doesn't cope with Base64 strings including new line characters. Unfortunately, these are often included by default when you pipe to base64.Supplying a string with new lines causes this action to fail with
base64: invalid input
. I can replicate the problem locally with the following two lines:It looks like a simple fix - if we quote the environment variable properly then decoding works correctly. I'll raise a PR.