Anton Tayanovskyy
Anton Tayanovskyy
Thanks for letting us know @ollaw - this is one of several issues where the provider needs an explicit state migration for this resource but is currently lacking one. Very...
Yes, upstream is using https://docs.grit.io to migrate sources but have provided no facilities to migrate the state. One alternative to migrating the state is importing it from the cloud -...
It appears there is some complicated upstream evolution history here that might be causing this problem. https://github.com/hashicorp/terraform-provider-aws/commit/a00ceec58405fb4f1ed0989f815e51b72d05b179 removes cluster_mode parameter that had a complex type https://github.com/hashicorp/terraform-provider-aws/commit/f893c221f533205c3f59588686858dec3a5316b8 reintroduces cluster_mode of string...
Thank you for filing this issue @JustASquid, could you add a quick repro program to make it easier to reproduce this exact issue. Thank you.
With https://github.com/pulumi/pulumi/issues/12154 feature we could one day direct the user to transforms or emit warnings on unused ignoreChanges accordingly.
go: github.com/pulumi/pulumi-terraform-bridge/[email protected]: verifying module: github.com/pulumi/pulumi-terraform-bridge/[email protected]: Get "https://sum.golang.org/lookup/github.com/pulumi/pulumi-terraform-bridge/[email protected]": net/http: TLS handshake timeout Perhaps expected this time around CC @guineveresaenger
Indeed, this is very unfortunate. Are some of the resources more important for your use case than other resources? Trying to see what our options are here, fixing the entire...
As a workaround it should be possible to unit test in languages other than Node where the overlays are not present perhaps, like Python.
From ``` new aws.iam.RolePolicyAttachment("test-policy", { policyArn: "test", role: "test", //works }, ); ``` Another workaround would be to use the string-passing forms instead of the overlay union types correct?
Got the same issue in Terraform when an unknown is passed to handler. We will need to file an upstream issue. Suspect missing/unknown distinction in the internals of SDKv2 TF...