[EPIC] WIP Cross-testing for Configure

[iwahbe]

We have made tremendous progress on testing in the bridge: cross-test, providertest and replay testing have made it much easier to write and maintain high quality tests of the bridge. cross-test has crucially allowed us to start comparing our behavior directly to Terraform. Now that we've written the testing libraries, we need to actually write tests.

In testing configure, we need to assert that values passed into Configure are available later on (in resources and datasources). Since the engine always passes secrets on Configure.

In addition to TF cross-tests, we need to test the behavior of resources and datasources when a provider is configured with an unknown value.

SDKv2

Each issue corresponds to a file¹ in pkg/tfbridge/tests/. The expectation is that future (and current) maintainers should be able to check if a feature is under test by going searching for a test file in pkg/tfbridge/tests/ that applies to the area under test.

PF

Each issue corresponds to a file¹ in pkg/pf/tfbridge².

Cross-test improvements

• Cross-test unknown values #1858 (required for testing unknown values, SDKv2 & PF)
• Assert full equality on *schema.ResourceData in SDKv2 cross-tests #2521 (tightens asserts, can be added after tests, SDKv2)

Footnotes

1. The file may already exist, or it may need to be created. ↩ ↩²

2. The path is different for PF and SDKv2 because SDKv2 cross-tests transitively imports pkg/tfbridge. ↩