I noticed that when using drone deploy secrets are not exposed to the job.
I’m running this command: drone deploy <repo> <build_number> <environment> -p PACKAGE=<some_package>
Maybe the fact that I’m using a parameter for the deploy somehow creates an issue?
When using the deploy directly, everything works fine.
I noticed a similar problem but it seems that --local is the problem there, prbably unrelated to this: