BUGFIX: use ListType
of ObjectType
for Computed
attributes instead of Blocks
#246
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.
Closes #244
Blocks
, on a protocol-level, don't support expressing the attribute of beingComputed
:terraform-plugin-framework
doesn't support it (yet?).But in our case it's possible to just do away with
Blocks
for thetls_certificate.certificates
, and instead define an attribute of typeListType
, that carries anObjectType
. By using an actualAttribute
, we can then express the fact that this is aComputed
attribute of the data source, and has such it's not expected to have a value until theAPPLY-PHASE
of Terraform. That will make the error encountered by practitioners in #224 go away.NOTE: We CANNOT use
Attribute.NestAttributes
for this, as that would break the compatibility with Protocol 5, i.e withTF >= 0.12
.