When using a secrets-file, if any of the secrets files do not assign a value to the secret, it results in the drone exec output having a bunch of extra asterisks in the output.
The build works fine when the secret is defined as “mysecret=secret”
But when passing an “empty” secret, the build output looks like:
In this case the secret is defined as “mysecret=”
It seems that Drone is using https://github.com/joho/godotenv#usage for secret file formats - and it’s quite possible this secret definition is just plain wrong per the gotdotenv spec, but I would expect an error or for the secret to be ignored instead of the confusing build output.
Here’s a repo that demonstrates the issue: https://github.com/ryanclemson/drone-logging-asterisks-from-secret
Run “make install-good” for a the first scenario, and “make install-bad” for the second
Obviously, this not a show stopper bug. Reporting it here so it can get addressed, or at a minimum, other folks googling for answers can find this if they happen to find asterisks (********) polluting their output.
P.S. Thanks for supporting Drone! We love it!