Ian Wahbe

@notdodo The best way to migrate **now** is with aliases: Old: ```yaml name: dev-yaml runtime: yaml resources: network: type: cloudflare:AccessPolicy properties: decision: allow name: my-policy accountId: ****************** includes: - everyone:...

If cloudflare has changed the arguments to these resources or their semantics, then migration will be trickier.

Let's leave it open to track #986.

Hi @OckhamOdyssey, thanks for opening an issue. It looks like the import should have included fields for `self_hosted_domains`, but it doesn't. We'll take a look and try to figure out...

@kramhuber Is this still a problem for you? This is working fine for me (MacOS, Chrome):

Hi @mikocot. I'm sorry your hitting this error. Unfortunately, this is almost definitely a bug in the upstream provider: [cloudflare/terraform-provider-cloudflare](https://github.com/cloudflare/terraform-provider-cloudflare). A pulumi level fix would be very similar to the...

Hi @williamsbdev. I'm sorry to hear that. I'm pretty sure that the underlying problem is where we generate these functions, so I'm going to move this issue to pulumi/pulumi.

@williamsbdev Can you try again with `@pulumi/pulumi` set to `3.136.0`?

Hi @JoshuaWR. Thanks for getting back to me. The 65.77.1 releases point to the correct commit in GitHub, but pkg.go.dev (which go mod uses) cached the wrong commit. My best...

Reiterating a message from [Pulumi's internal slack](https://pulumi.slack.com/archives/C02FXTZEZ6W/p1728663268866229?thread_ts=1728647943.286109&cid=C02FXTZEZ6W): The providers team has moved away from slack alerts to issue creation, since that tracks resolution of the issue. Our ideal case is...