Posted June 14, 2021
For a while now, I’ve used Rush to manage and deploy a number of Cloudflare Workers from a monorepo. It’s been great for me so far, offering incremental builds and support for alternative package managers like PNPM.
One thing Rush leaves to the discretion of maintainers is secrets management. Given tooling and infrastructure can vary drastically between organisations and even individual projects, there’s nothing wrong with this decision. However, it has lead to me implementing my own less-than-desirable setup.
- Every project follows its own
build.shscript to load secrets, build and deploy
- Cloudflare-related credentials are read from a shared script
- Workers that need third-party API tokens read them from their own
This works, but it has a number of shortcomings. What if a worker needs to be deployed to a different Cloudflare zone (website) from every other worker? How do I manage/keep track of all these
I ended up looking to the
pass password manager. I’ve found it convenient for my personal projects, as it leverages my existing GPG setup and makes it easy to store/retrieve secrets from the command line.
A few changes later, and now the build scripts for each project are explicit about what secrets they need! Here’s an abridged example.
- source ../../set-cloudflare-secrets.sh + export CF_ACCOUNT_ID=$(pass show workers/cloudflare-account-id) + export CF_API_TOKEN=$(pass show workers/cloudflare-api-token) + export CF_ZONE_ID=$(pass show workers/cloudflare-zone-id-nicholas.cloud) - source .env + export MAILGUN_API_KEY=$(pass show workers/newsletter-subscription-form/mailgun-api-key) + export EMAIL_SIGNING_SECRET=$(pass show workers/newsletter-subscription-form/email-signing-secret)
I did find an interesting interaction between Rush and the GPG agent. Rush attempts to build projects in parallel where possible, and if too many processes are decrypting secrets at once the GPG agent will return a
Cannot allocate memory error.
Thankfully this can be fixed by adding the
--auto-expand-secmem option to the agent’s config. This allows gcrypt (used by GPG) to allocate secure memory as needed.
# ~/.gnupg/gpg-agent.conf auto-expand-secmem
With the GPG agent restarted, I can now build many projects with secrets in parallel! It’s also good to have my secrets sitting safely outside source control, stored in a place where I can easily back them up.
pass to fetch and decrypt secrets does admittedly add a few seconds to each build. Thankfully, Rush’s parallelism keeps the overall build comparatively fast. In my eyes, the tradeoff is worth it.