Ian Wahbe

Hi @FooBartn. Thanks for pointing this out. That's our bad. `BucketServerSideEncryptionByDefaultSseAlgorithm` is an enum with 3 values: https://github.com/pulumi/pulumi-aws-native/blob/e30801434c72287a89eb17735c5903a273e27c0a/sdk/go/aws/s3/pulumiEnums.go#L3518-L3524 You can run the code you posted by replacing `s3.BucketServerSideEncryptionByDefaultSseAlgorithmArgs{}` with your...

Closing as state. If you are still experiencing this problem, please file a new issue.

Hi @rhuanbarreto. Thanks for opening an issue! I agree that we should correctly deploy the `synapse.BigDataPool` as described. To help us reproduce the issue, can you post the code you...

Thanks @rhuanbarreto.

It looks like this is fixed in pulumi-auth0. On `auth0.Connection.options` there is a `mapUserIdToId` field: ```yaml name: dev-yaml runtime: yaml resources: connection: type: auth0:Connection properties: strategy: google-workspace options: mapUserIdToId: true...

The `auth0` provider now accepts a `apiToken` argument, though to avoid https://github.com/pulumi/pulumi/issues/4981 I would pass `apiToken` via an environmental variable. @stephenbawks, if this wasn't what you meant please open a...

It looks like upstream just merged a fix in this area: https://github.com/auth0/terraform-provider-auth0/pull/1024. As soon as they make a release, we'll update the pulumi provider.

Hi @damey2011. Thanks for reporting this issue.

For provider maintainers: I have confirmed that the perpetual diff is still present on 3b48c17c6debdf87019c917cb1b9a16e0d6a8239, which includes the PRC rollout. We can repro in YAML with: ```yaml name: dev-yaml runtime:...

Hi @Navigatron. Thanks for letting us know about this issue.