handle panic on parse workers kv id #1635
Merged
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.
Currently the provider panics when an invalid id is used to import a
cloudflare_workers_kv
resource.For example
e8b09ec03fe84a7db31416f050c1d75c_test
instead ofe8b09ec03fe84a7db31416f050c1d75c/test
will attempt to access an index out of range.This change will throw an error explaining the issue and the id that is causing the panic instead of the provider panicking.