Skip to content
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.

allow kv_namespaces in toml #1409

Merged
merged 1 commit into from Jun 24, 2020
Merged

Conversation

EverlastingBugstopper
Copy link
Contributor

fixes #1408 -

when KV namespace support was initially added to Wrangler, we documented using `kv-namespaces` in `wrangler.toml`. Unfortunately, the `-` was not consistent with other fields such as `zone_id` and `account_id`, so the decision was made to allow both `kv-namespaces` and `kv_namespaces`. When this change was introduced, it worked with top level `kv_namespaces` entries, but not in environments. This is now fixed! You can now use `kv_namespaces` everywhere you can use `kv-namespaces`.

@EverlastingBugstopper EverlastingBugstopper merged commit 9d01d9b into master Jun 24, 2020
@EverlastingBugstopper EverlastingBugstopper modified the milestones: 1.11.0, 1.10.3 Jun 26, 2020
@EverlastingBugstopper EverlastingBugstopper deleted the avery/fix-namespace-alias branch August 3, 2020 17:08
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Environment kv_namespaces not being parsed into the config
2 participants