[EPIC] Cross-testing coverage for Create

[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.

We are starting with create because it is one of the simplist CRUD methods. It allows us to lock in correct behavior on sending values, defaults validators, etc before we move onto more complicated interactions like Diff/Update (Plan).

Many tests aren't really specific to Create, but are instead about converting values. These tests will be implemented against the crosstests.Create verb, but will effectively cover all verbs (since they use the same code path).

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

• Add Create for PF cross-testing #2534 (required for cross-tests, PF)
• Cross-test unknown values #1858 (required for testing unknown values, SDKv2 & PF)
• Assert on outputs in SDKv2 Cross-tests [Create][SDKv2] #2523 (required for output tests, SDKv2)
• Assert on outputs in SDKv2 Cross-tests [Create][PF] #2524 (required for output tests, 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. ↩

[cleverguy25]

Added to epic https://github.com/pulumi/home/issues/3657