Anton Tayanovskyy

This seems benign, just automation is not prepared to handle lack of changes to SDK? Strange that it didn't happen before. Taking a Quick Look.

I'm glad you found a workaround! I am curious does the same thing happen for you when you run `pulumi` binaries like Pulumi CLI itself? Doing a bit of of...

Skimming through https://github.com/pulumi/pulumi-aws-native/blob/master/aws-cloudformation-schema/aws-rds-dbinstance.json it appears we're still waiting for a change in Cloud Control API, but please let us know if we're missing something obvious here. Thank you!

@flostadler suggests https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html is relevant here, checking up on it.

Regarding the AWSCloudFormation DeletionPolicy, looks like we are not sure yet how that maps to the Cloud Control API and hence this provider, unfortunately, will require some further research as...

Would appreciate some repro code here to diangose this further. Thank you!

Thanks for your patience @tlinhart , I was able to repro. It looks like we might be having an issue either with the core Pulumi SDK or codegen for Python...

Related https://github.com/pulumi/pulumi/issues/12710

``` Updating (dev) View in Browser (Ctrl+O): https://app.pulumi.com/anton-pulumi-corp/awsx-1253/dev/updates/4 Type Name Status Info Type Name Status Info + pulumi:pulumi:Stack awsx-1253-dev creating (1091s) + ├─ awsx:ec2:DefaultVpc default-vpc created (2s) Type Name Status...

Thanks so much for the repro!