Anton Tayanovskyy

I've only tested IMDS(v2) not IMDS(v1) but I have no reasons to believe that reverting to defaults wouldn't fix that as well.

Would it be possible get a minimal program demonstrating the issue (pulumi up && pulumi destroy)? And also the output of `pulumi about`. Much appreciated.

Change schema, remove Computed, add Default

Reviewing this patch lightly again today as @corymhall mentioned it's part of the friction in a scheduled upstream upgrade in https://github.com/pulumi/pulumi-aws/pull/3959 I think `GetRawConfig()` used to incorrectly return null in...

I'm sorry the documentation is not clearer at the moment. This form is supported but emits a deprecation warning as it is deprecated in pulumi-aws following the upstream deprecation: ```python...

Looking at this today since https://github.com/pulumi/pulumi-aws/pull/3959 it's involved in a major upgrade. Looks like the bridge fix as yet is unreleased, but we should be able to close it once...

I'm sorry this does not work as expected! Would it be possible to add a quick Pulumi program that provisions a "aws:ec2/subnet:Subnet" with a child "aws:ec2/routeTableAssociation:RouteTableAssociation" that would then be...

Great work! I'd patch and release first and propose upstream PR, any reason to keep our users waiting? One reason would be if there is uncertainty or risk in the...

> I'd say the main risk with the patch is the maintenance effort. If that becomes the problem we can revert right. I'm for merging.

Opting against this route.