The cross-testing in #1801 is as yet unable to verify handling unknown values. The limitation here is that the drivers
use HCL and Pulumi YAML to feed data into the respective CLIs for an end-to-end test, but there are no literals for
unknown values. To emulate this one would need to emit an additional helper resource reference to simulate an
unknown-at-preview output in the provider.
In addition, it is worth verifying if Block-typed TF schemas can ever accept unknown values at runtime; if not,
randomized generation should not try to sample them probably, and we would need to confirm that Pulumi bridged providers
reject them for blocks.
The cross-testing in #1801 is as yet unable to verify handling unknown values. The limitation here is that the drivers use HCL and Pulumi YAML to feed data into the respective CLIs for an end-to-end test, but there are no literals for unknown values. To emulate this one would need to emit an additional helper resource reference to simulate an unknown-at-preview output in the provider.
In addition, it is worth verifying if Block-typed TF schemas can ever accept unknown values at runtime; if not, randomized generation should not try to sample them probably, and we would need to confirm that Pulumi bridged providers reject them for blocks.