Wrangler automatic resource provisioning

Hey folks, you might have already noticed the changelog on this, but also very open to any feedback you have on this change. We think it's a good one, but we still have a few internal discussions unresolved and perhaps the community feedback can help us! https://x.com/MattieTK/status/1982963805417079261
Matt 'TK' Taylor (@MattieTK)
New from wrangler, no more complaints for missing IDs in your config file. šŸ†• Now we generate D1, KV, and R2 resources automatically for you when you don't specify them on deployment. All kudos to @samuelpmacleod who was working on this well before I joined.
From Matt 'TK' Taylor (@MattieTK)
X
2 Replies
TK
TKOP•4w ago
Any thoughts in the thread šŸ˜„
Isaac McFadyen
Isaac McFadyen•4w ago
My initial thoughts are that it seems somewhat dangerous. I can imagine forgetting an ID when adding a resource, quickly deploying without fully reading the output, and then trying to e.g. debug why my KV namespace is empty when I was expecting values. Was there a discussion around whether to prompt the user with a yes/no? That feels a touch safer IMO. šŸ¤” Often if a deployment complains it's missing an ID that isn't an annoyance but just the CLI working as it's supposed to and not touching resources I didn't expect it to.

Did you find this page helpful?