Anton Tayanovskyy

It's difficult to read such a long type printout, but it could be that it's failing to match null against the expected type as in https://github.com/pulumi/pulumi-aws/issues/2534 - if the root-cause...

It would be a great help if we had a quick repro here I could try some possible fixes on, much appreciated.

Added resources not in upstream

Well that's a good point; that's one way to make the argument; but the other argument is for testing this is strong too. We're maintaining legacy bucket when upstream doesn't,...

Changes tags behavior; wonder if this is sitll needed post tags refactor?

Context propagation looks benign

``` ~ aws:wafv2/ruleGroup:RuleGroup: (update) [id=636067c5-d5de-406c-a09a-7fa1848b2cdd] [urn=urn:pulumi:dev::aws-3190::aws:wafv2/ruleGroup:RuleGroup::waf] [provider=urn:pulumi:dev::aws-3190::pulumi:providers:aws::prov::599aac36-1f59-4df1-906a-42f23a95f15b] ~ rules: [ ~ [0]: { ~ action : { + __defaults: [] ~ block : { + __defaults: [] } } ~...

If this is the right call, something like this https://github.com/pulumi/pulumi-aws/pull/3897 could be used to work around if we cannot fix the root cause in the bridge.

I am sorry this is not working as expected. This is a very interesting issue, thank you @jesperseverinsen for filing this with a repro, my team will have a look...

Hi @oboukili thank you for reporting this and sorry that Pulumi is not doing what you need here. It sounds like you are running Pulumi against the same stack in...