Think I found a bug in handling mis-mapped secrets with drone6+. Consider the following syntax:
- source: my_secret
- target: secret_var
Accidentally adding the second dash means we’re declaring a target without a source. When the build runs, you get the following error:
Error response from daemon: invalid environment variable: =ACTUAL_SECRET_VALUE
Can the mapping be updated to return a better error when you declare a target without a source, and also not leak the secret value?