[Epic] Terraform Bridge - Plugin Framework Support

[t0yv0]

Continued support for bridging Terraform Plugin Framework based providers to Pulumi.

The work in progress is available as pf Go Module which includes a README with instructions on trying it out.

For an example of a production provider utilizing the current support, see pulumi-random.

References

• Support channel #plugin-framework in Community Slack.
• Internal Design Doc

Timeline

2023 Q2

Providers

Bridged providers that need this work to continue releasing up-to-date with upstream:

• pulumi-aws
• pulumi-gcp
• pulumi-cloudflare

Work Items ⚙️

M0.87

• Fix #941: SetAutonaming panics when used with Plugin Framework #943
• Breaking: Require MetadataInfo for Plugin Framework #964
• Cannot derive an encoder for property "timeouts": expected a Map, got tftypes.Object #968
• panic: nil pointer on pulumi up with experimental Plugin Framework resource #969
• Schema for Plugin Framework providers now recognizes ObjectTypeable #973
• Fix recognizing MaxItems=1 list blocks in Plugin Framework #984
• Remove a panic when computing pf/tfgen not_supported warnings #985

M 0.88

• Plugin-framework based providers fail to support non-string configuration properties #1032
• Cannot reference an attribute marked as secret in schema for Invoke outputs #998
• Fix recognition of deeply nested block schema for Plugin Framework #1030
• [Plugin Framework] Support populating defaults from DefaultInfo #938
• User-provided secret bits are not preserved through resource properties #1028
• AWS skip_metadata_api_check not working with Plugin Framework #1074
• [Plugin Framework] Verify inherited client configuration support #754

M 0.89

• [Plugin Framework] Implement CheckConfig properly #821
• [Plugin Framework] PreConfigureCallaback Support #935
• [Plugin Framework] Validate resource configuration in Check #822
• [Plugin Framework] Support computing DetailedDiff in Diff method for best CLI experience #752
• [Plugin Framework] Support Private State #747
• Community provider fails in tfgen with "could not validate provider config ... 'foo.pluginDownloadURL'." #1169
• Ensure missing required provider property failures surface in Pulumi CLI #1173

M 0.90

• Empty bridge-metadata.json file is expected to be present #1019
• [Plugin Framework] Support AutoName #917
• ComputeDefaults and AutoAliasing don't work on pure PF providers #1197
• Cleanup interfacing with Plugin Framework #1210

Out of scope

These items will remain as issues in the repo (backlog) until we know of more concrete use cases. Please feel free to upvote any of these or add new issues as it helps us prioritize to address real needs:

• [Plugin Framework] Implement the DiffConfig method #753
• [Plugin Framework] Consider supporting running acc tests against bridged provider #829
• [Plugin Framework] Propagate ProviderMeta correctly #794
• [Plugin Framework] Stable and ForceNew properties support #936
• [Plugin Framework] Support Transform Transformers #937
• [Plugin Framework] Mark manually renamed AutoName resources as DeleteBeforeRelpace #930
• [Plugin Framework] Support UniqueNameFields #931
• [Plugin Framework] Support v1.2.0 #918
• [Plugin Framework] Compute StableKeys in Diff #824
• [Plugin Framework] Ensure custom timeouts work properly #827

[t0yv0]

Per conversation with @AaronFriel this epic was getting a bit crowded and we've moved out tasks pertaining to muxed provider support into a separate epic: #981 ; will continue tracking general support and fixes for Plugin Framework bridging.

[t0yv0]

The latest version https://github.com/pulumi/pulumi-terraform-bridge/releases/tag/pf%2Fv0.13.0 is quite capable and will be shipping in pulumi-aws v6. There's a few incomplete items that remain in the repo backlog. As always upvotes are highly appreciated to help us prioritize working on items that matter to end-users. Closing this for now.