[draft] Wrangler Resource provisioning #6462
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR solves / how to test
This is a draft PR demonstrating a possible way to do resource provisioning with Wrangler. It currently supports R2, KV, and D1. All you need to do is run
wrangler deploy
against awrangler.toml
file with the ID information missing (namespace_id
/bucket_name
/database_id
) and Wrangler will prompt to create the resource during the deploy. Wrangler will use aninherit
binding if the resource already exists, to get around the lack of ID information being persisted.Author has addressed the following