This repository has been archived by the owner on Sep 3, 2024. It is now read-only.
[RM-5823] Fix type mismatch when constructing cty value #176
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.
The TF loader uses two representations of the document:
[]interface{}
for arrays,map[string]interface{}
for objects, etc.cty
library.When dealing with variables, we must sometimes convert from (1) to (2).
cty
requires lists to be homogenous. This is usually not a problem since the types
in the schemas enforce this; however, in some cases we don't have these schemas,
and this list ends up looking heterogenous:
We work around this by using a tuple instead of a list which allows for
different types.