Daniel Bradley

Unfortunately there's been no response yet.

This is probably dependant on #124

Hi, thanks for the feedback. Unfortunately, the [AWS specifications](https://github.com/pulumi/pulumi-aws-native/blob/master/aws-cloudformation-schema/aws-ecs-taskdefinition.json#L806-L813) don't currently indicate which are required fields so we're unable to geneate this metadata for our provider. Hopefully this will be...

Another workaround here is to use the lambda Permission resource from the bridged AWS provider until this is fully supported by CloudControl. ```typescript const publicInvokePermission = new aws.lambda.Permission("public-invoke-permission", { function:...

Unfortunately, this validation and these errors are provided by the Azure API – we just pass on any error message as error output. This most likely needs addressing by Azure,...

The repro link no longer works, please could you provide a new copy of the code @zbuchheit

Just rebuilt a test case for this. To keep creating new identities and assigning them, change the value of `TEST_N` on each run e.g. `TEST_N=5 pulumi up --skip-preview` ```typescript import...

After running 10 iterations of the above test I've not managed to reproduce the issue. It's possible that this might have been affected by https://github.com/pulumi/pulumi-azure-native/pull/3042 in release [v2.29.0](https://github.com/pulumi/pulumi-azure-native/releases/tag/v2.29.0) which could...

Looking at the code at version 2.10 of the provider, this is the source of the error: https://github.com/pulumi/pulumi-azure-native/blob/cf2ad6293aef49de48225b514fdb5f2246750f6c/provider/pkg/provider/provider.go#L904-L911 This helps us understand the original error message reported, just to help...

I've dug through the logs but can't identify anything we can do here to resolve the issue of what appears to be Azure's internal replication latency. Marking this as blocked...