decocms / decocms/blocks

deco-migrate: wrangler.jsonc usa 'dev-sites-kv' placeholder inválido como KV namespace ID

Open
#486 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5
Forks
2
Avg merge
20h 12m
Merged PRs (30d)
36

Description

Gap encontrado: portal-davinci migration run (2026-08-20)

Fase

migrate-script → geração de wrangler.jsonc

Problema

O template gera:

"kv_namespaces": [{ "binding": "SITES_KV", "id": "dev-sites-kv" }]

O campo id deve ser um UUID de namespace KV real (ex: 3123e62af7c3492bb867f9bbeaba31e5).
O valor "dev-sites-kv" causa erro no deploy:

KV namespace 'dev-sites-kv' is not valid. Please verify the namespace_id [code: 10042]
Fix sugerido

O template-bootstrap ou pós-migrate deve:

  1. Criar o KV namespace via wrangler kv namespace create "<site-name>-sites-kv"
  2. Substituir o placeholder pelo ID retornado

Ou alternativamente: deixar o campo vazio/comentado com instrução explícita para o usuário criar antes do primeiro deploy.


Transferida de decocms/parity#238 (bug de template do deco-migrate / @decocms/blocks-cli, fora do escopo do repo parity).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the migrate-script phase that generates wrangler.jsonc, then inspect the template-bootstrap and post-migrate paths mentioned in the issue. Reproduce the generated kv_namespaces entry and check how namespace creation or user instructions are handled before deployment. Done means the migration no longer produces the invalid dev-sites-kv placeholder and the resulting configuration has a clear valid-namespace path.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cloud, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.