Introducing Deploy Buttons

cloonan · August 20, 2020, 10:51pm

wighawag · November 15, 2020, 10:33pm

Hi,
Deploy buttons are great!
I have a question though. How do we deal with KV namespaces ?
I currently associate the KV name to id in wrangler.toml but how does it work for user deploying a new worker with id that do not match ?

Is there a way to ensure that when they deploy they have their KV automatically created ?

eidam · November 16, 2020, 12:02pm

Afaik there is no support for auto-creating KV namespaces in Wrangler Actions. However, I managed to work around with preCommand

        preCommands: |
          wrangler kv:namespace create KV_NAMESPACE_NAME
          apt-get update && apt-get install -y jq
          kv_namespace_id=$(wrangler kv:namespace list | jq -c 'map(select(.title | contains("KV_NAMESPACE_NAME")))' | jq ".[0].id")
          echo "[env.production]" >> wrangler.toml
          echo "kv_namespaces = [{binding=\"KV_NAMESPACE_NAME\", id=${kv_namespace_id}}]" >> wrangler.toml

github.com

eidam/cf-workers-status-page/blob/main/.github/workflows/deploy.yml#L25


      
          steps:
          - uses: actions/checkout@v2
          - uses: actions/setup-node@v1
            with:
              node-version: 12
          - run: yarn install
          - run: yarn build
            env:
              NODE_ENV: production
          - name: Publish
            uses: cloudflare/[email protected]
            with:
              apiToken: ${{ secrets.CF_API_TOKEN }}
              preCommands: |
                wrangler kv:namespace create KV_STATUS_PAGE
                apt-get update && apt-get install -y jq
                export KV_NAMESPACE_ID=$(wrangler kv:namespace list | jq -c 'map(select(.title | contains("KV_STATUS_PAGE")))' | jq -r ".[0].id")
                echo "[env.production]" >> wrangler.toml
                echo "kv_namespaces = [{binding=\"KV_STATUS_PAGE\", id=\"${KV_NAMESPACE_ID}\"}]" >> wrangler.toml
                [ -z "$SECRET_SLACK_WEBHOOK_URL" ] && echo "Secret SECRET_SLACK_WEBHOOK_URL not set, creating dummy one..." && SECRET_SLACK_WEBHOOK_URL="default-gh-action-secret" || true
                [ -z "$SECRET_TELEGRAM_API_TOKEN" ] && echo "Secret SECRET_TELEGRAM_API_TOKEN not set, creating dummy one..." && SECRET_TELEGRAM_API_TOKEN="default-gh-action-secret" || true

adaptive · November 16, 2020, 1:14pm

We might have soon, free Workers KV to try across accounts, that will solve this issue.

adaptive · November 16, 2020, 8:38pm

Here it is:

Topic		Replies	Views
KV namespace binding at environment level Cloudflare Workers	2	3107	February 7, 2020
Wrangler Publish erasing KV Namespace Binding Cloudflare Workers dash-getting-started	3	3304	December 13, 2019
KV Bindings Command Cloudflare Workers	2	2594	June 20, 2021
How to use multiple KV in a worker? Cloudflare Workers	8	1674	August 31, 2023
My KV binding is not being set by my wrangler.toml file when deploying to my production environment Cloudflare Workers	1	1517	February 13, 2025

Introducing Deploy Buttons

Related topics