WorkersScript resource `migrations` not working since upgrade to upstream v5.8.2

[user-0a]

Describe what happened

It appears that the migrations field of the WorkersScript resource was removed in this PR upgrading to upstream v5.8.2.

I believe this is an oversight as it does not appear that it was removed from the upstream terraform provider: https://github.com/cloudflare/terraform-provider-cloudflare/blob/7358f25cd2725f2a19fff0321fc19a166f05c0ef/internal/services/workers_script/model.go#L106

This is currently impacting deploying workers with Durable Objects

Sample program

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[corymhall]

@user-0a it looks like the migrations field was changed to a write-only property which we do not support yet. We will be able to add this field back when we add support for this type of attribute.

[user-0a]

Ah I see, thank you.

We tried working around this using the WorkerVersion resource with migrations but it looks like there is a bug there as well (not sure if it's due to the upstream or bridge incompatibility).

We will continue looking into workarounds, but I think that it would be great to get write-only support soon as it seems that it will make using Durable Objects not possible / very painful without it.

[guineveresaenger]

Hi @user-0a - it is additionally the case that WorkersScript is no longer recommended: https://www.pulumi.com/registry/packages/cloudflare/api-docs/workersscript/ - it might be worth it to explore the suggested alternatives.

[user-0a]

Thank you, will check it out!

[user-0a]

It appears that we can't migrate as WorkerVersion requires write-only attribute asset.jwt to upload assets :(