Prevent panic on null values when iterating over map elements #413
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.
📚 Context
I was writing a small module to create organizations from a list:
then defined my module as such
However, when I tried to apply, I got the following crash from this provider:
🔧 Changes
This checks
IsNull
oncty.Value
before callingAsString
which ensures that the provider doesn't panic if a value is missing. The crash is then replaced by:🔬 Testing
I expanded the unit tests to check the edge case. Also I used this minimal reproducible example to check (crash with v0.40):
Note: you will only get the crash on apply, not during planning, so if there are no difference to apply, it will just exit normally. Change the display name and try to apply and the crash will happen.
📝 Checklist