flatten: only DynamicVal should cause flatten to become unknown, not a null dynamic value. #110
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When flattening a list of arguments, the special case of a `null` dynamic value should not force the result to be unknown. We do not check directly for "IsKnown" here, because it is specifically the dynamic type which will cause `flatten` to become unknown, while unknown values alone can be preserved preserved.
jbardin
changed the title
apparentlymart
approved these changes
Jul 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When flattening a list of arguments, the special case of a
nulldynamic value should not force the result to be unknown. We do not check directly for "IsKnown" here, because it is specifically the dynamic type which will causeflattento become unknown, while unknown values alone can be preserved preserved.hashicorp/terraform#29099