Anton Tayanovskyy

That's reasonable, we could build https://github.com/pulumi/pulumi-aws/issues/3022 first and then rearrange things so that the provider modifications happen so that upstream tests exercise our patches, it could be very valuable here.

Notes from team discussion: we can try running some upstream tests over PF, but probably targeting all modules is too hard; we'll target a few modules, exclude upstream tags tests...

I can try to see if actual allocation without any subnetSpecs differs between legacy and auto allocator.

It looks like legacy and auto strategies are generating the same layout. I've confirmed by provisioning this program on the prod version of the provider and testing upgrading the provider...

@corymhall can I have a quick review here? This simplifies case analysis in the PR that supports using IPAM with awsx.ec2.Vpc.

One interesting user story: https://levelup.gitconnected.com/my-journey-with-pulumi-and-the-serverless-framework-2b1398ee581a - there might be additional complications for CallbackFunction coming from closure serialization, but even if those were not fully addressed if we could guide users...

Thanks so much for the issue report @EvanBoyle - my team will have a look as time permits. Digging through the test suite I note that while we have TestAccTopic...

I can confirm I can reproduce this, self contained version of the repro: ```typescript import * as aws from "@pulumi/aws-native"; const stackName = "sn"; const domainName = "stuff.com"; const archive...

From the logs: ``` aws-native.Create(urn:pulumi:dev::pulumi-aws-native-1748::aws-native:ses:MailManagerRuleSet::sn-mail-rules).CreateResource "AWS::SES::MailManagerRuleSet" POST / HTTP/1.1 Host: cloudcontrolapi.us-west-2.amazonaws.com { "ClientToken": "6d07ff05-df95-43ba-9af2-4b603d5e9288", "DesiredState": "{\"RuleSetName\":\"archive\",\"Rules\":[{\"Actions\":[{}],\"Name\":\"archive\"}]}", "TypeName": "AWS::SES::MailManagerRuleSet" } ```

Curious what you meant by "problem with capitalization", at a first glance it appears the rule definition is not making it into the request at all. We will need to...