Anton Tayanovskyy

Both attributes seem to be Optional+Computed meaning that they can be set by either the provider or the user, and Pulumi maps them to inputs and outputs.

Curious how this works in Terraform proper, checking.

Looks like in TF there are no warnings on import but https://spacelift.io/blog/importing-exisiting-infrastructure-into-terraform is suggesting to manually edit the program at which point this issue can be manually resolved .

Unfortunately this reproduces still. The root cause here is pulumi/pulumi-terraform-bridge#186

If anyone is still affected by this, I'd appreciate a quick repro of a Pulumi program demonstrating the problem, it would really helps us narrow this down and look at...

So apparently this issue pertains to containerDefinitions of ecs.TaskDefinition that is typed as string but represents a complex JSON structure. #1985 is likely correctly identified as a root cause -...

We really need this for pulumi-aws https://github.com/pulumi/pulumi-aws/issues/2246 and possibly more. Couple of other thoughts: - looks like it does not apply to import, which I think is good; import should...

Nit: build times won't be affected as much since example generation is cached. Otherwise would be quite beneficial.

This is the first draft of my thoughts here but still actively discussing entangled resources with @EronWright and correlating some K8S use cases to explore the design space, especially for...

Perhaps separate ticket for that? Getting good pushback on this issue as it's rightly being pointed out that protocol changes should be well motivated. I think we need some end-user...