Anton Tayanovskyy

I have confirmed that https://github.com/pulumi/pulumi/pull/14007 caused the change in behavior by interacting in an unexpected way with the asset-handling code in the bridge. Building 6.6.1 of the provider against v3.90.1...

I have passed on https://github.com/pulumi/pulumi/issues/15729 to the core team, the evidence is that it's likely once we have that fixed we can remediate the issue here. Thanks for your patience...

Still awaiting a pulumi release (v3.111.1 does not contain the fix yet).

I can confirm this is happening. Using something like this to delete tags in the CLI: > aws s3api delete-bucket-tagging --bucket my-tf-test-bucket-grr This works fine for BucketV2, confirmed: ``` const...

3m:32s prerequisites job possible on the warm cache it seems: https://github.com/pulumi/pulumi-aws/actions/runs/8445164030/job/23132412156

Closing, most of this has been upstreamed to ci-mgmt and the bridge. We can still try to remove P=2 compilation parallelism limits that were there to limit RAM use, though...

I think I might be misremembering something, we need to measure again. The investigation started with https://github.com/pulumi/pulumi-cloud-requests/issues/313 And then we found that Go generics was doubling RAM consumption. But RAM...

Per @EronWright doing a stateful observation of a series of Check calls can help the provider detect this pattern and emit a warning so that the warning is more obvious...

Thank you for this valuable investigation @corymhall ! I am going to correlate a few comments from internal discussions here as well. Luke pointed out to https://github.com/pulumi/pulumi-policy-aws aka AWSGuard which...

> And even after the security group has been created and we know the id, we have no way of mapping that back to the original security group resource since...