Skip to content

feat: support RefreshBeforeUpdate for bridged providers #3140

@tmeckel

Description

@tmeckel

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

With PR pulumi/pulumi#19487 the Pulumi SDK allows to mark resources with RefreshBeforeUpdate: true so that Pulumi will perform a refresh on the resource regardless if the user has added --refresh to the pulumi command or not.

Because Terraform always performs a refresh on the state before calculating and differences and actions on resources, this feature is of great benefit for maintainers of wrapped Terraform providers because Terraform providers often rely on a refresh to be performed to trigger any (internal) updates on the managed resources. One example of this is the Pulumi Time provider, which wraps the Terraform Time provider. Practitioners often struggle when the time provider does not rotate, update, or change any resources because Pulumi did not perform a refresh.

pulumiverse/pulumi-time#59
pulumiverse/pulumi-time#70

If Terraform Bridge would provide support for RefreshBeforeUpdate those issues can be prevented easily by marking the relevant resources, so that a refresh cycle is always performed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions