Open royalnine opened 4 hours ago
To whoever might be experiencing the same. What fixed this for me was to get rid of the space in:
NODE_API_KEY: <PROJECT-ID>/<SECRET-NAME>
NODE_RPC_URL: <PROJECT-ID>/<SECRET-NAME>
to become:
NODE_API_KEY:<PROJECT-ID>/<SECRET-NAME>
NODE_RPC_URL:<PROJECT-ID>/<SECRET-NAME>
it did use to work with a space but 🤷
TL;DR
Hi all - we started experiencing an issue in our CI that all of our workflows depending on secrets retrieval from GCP started to fail. These workflows have not been touched for many months and suddenly started failing today.
Expected behavior
secrets retrieved from GCP
Observed behavior
FIrstly,
projects/<PROJECT-ID>/secrets/<SECRET-NAME>
is what we used and it was failing with:Notice the space after first
projects/
in the path and also duplication ofprojects/
andsecrets/
.Then I tried to bypass this by using a short path for latest versioned secret like:
<PROJECT-ID>/<SECRET-NAME>
and not it is failing with:in this one, please notice the space after
projects/
.Action YAML