Matthew (Matt) Jeffryes
Matthew (Matt) Jeffryes
yes, what Pulumi is sending is valid according to the schema despite not being what the API expects. You can see there's a top level SKU field in line 699:...
I believe that the source of the 404 is that we do a read of each resource immediately after creation (this improves consistency with later `refresh` commands). What's probably happening...
Thanks for reporting this @PierreBeucher and for links to the replaceContent API. This doesn't look like behavior we can generate from the API specs directly, so it will require some...
another issue encountering this in #3015 and #3023
Thanks for reporting this @hisuwh.
Thanks for filing this issue @nichitacebotari0. We'll have to check the schema to see why the change to the location parameter is not forcing a replace. As a workaround, you...
Thanks for reporting this @scottslowe; we'll take a look.
Thanks for the bug report @keidyz; there's a small chance this is related to the change in https://github.com/pulumi/pulumi-azure-native/pull/3076, would you mind seeing if you have the same problem using pulumi-azure-native...
Thanks for suggesting this @stfnzl and for sharing your workaround.
Sorry about the missing error message @moulip. Glad you found a workaround to debug and thanks for filing the bug report!