Notices by Marco 🦝 :verified: :grumpycat: (m2vh@mastodontech.de)

@jwildeboer @Codeberg

yeah. 🥳

Just by the power of fediverse.

-🫷😉👇_

@jwildeboer @Codeberg hmmm... May i suggest this version, but with the secrets declared? https://codeberg.org/jwildeboer/jwildeboersource/src/commit/bac77e219b9cce4925bdd7311e7b56f32e61b8ac/.woodpecker.yml

$${VAR_NAME} looks like the docs. But I'm missing the

secrets: [ secret1, secret2]

But i might be wrong, because i followed your files on my mobile phone, and missed something.

🤔🙏🤞

@jwildeboer @Codeberg the update would be the use of env vars in commands instead of referencing the secrets directly. That could explain the warning message that secrets are not allowed.

@jwildeboer @Codeberg my guess, because its yaml:

secrets: [token1, token2]

environment:
TOKEN_1:
from-secret: token1
TOKEN_2:
from-secret: token2

commands:
- echo ${{TOKEN_1}}
- echo ${{TOKEN_2}}

That's how i understand the docs

@jwildeboer @Codeberg found the warning. It looks like you need to paas the secrets into a setting or environment variable before using it in a command. Actually you use a declared secret. Maybe put
environment:
CBTOKEN_ENV:
from-secret: cbtoken

between your line 8 and 9
and reference in command like ${{CBTOKEN_ENV}}.

BTW:
The documentation is age-insensitive 😁.
It's just not clear. 😉

@jwildeboer @Codeberg maybe escape them when you use them? If they are preprocessed then :
echo $${CBTOKEN}

Should be resolved to :
echo tokenvalue

Your missing the {{}}?