Systematic diff in Elastic Beanstalk settings

[odusseys]

Running pulumi up with the same Elastic Beanstalk Environment settings twice will (almost) invariably lead to a diff being show when there is none.

Expected Behavior

There should be no diff and the Environment should not be updated.

Current Behavior

• The order of settings is randomly queried by pulumi and generates a diff if it is different from what pulumi finds in the declaration.
• the resource field of each setting, if left undefined in the declaration, is compared to an empty string when queried by pulumi.

Steps to Reproduce

1. Declare an aws.elasticbeanstalk.Environment with several settings (eg. a few environment variables)
2. Run pulumi up twice

[stack72]

Hi @odusseys

Just to get a little more flavour here - please can you tell me what version of Pulumi and Pulumi-aws you are using?

Thanks

Paul

[odusseys]

"@pulumi/aws": "^2.0.0",
"@pulumi/awsx": "^0.20.0",
"@pulumi/pulumi": "^2.0.0"

I installed the CLI & initialized the project yesterday btw

Edit: I also tried with the latest version of these packages, as the CLI does not initialize the project with them (could be considered an issue in itself btw), same problem :

"@pulumi/aws": "^3.1.0",
"@pulumi/awsx": "^0.21.0",
"@pulumi/pulumi": "^2.8.2",

[ffMathy]

This happens to me too. There is a previous issue #920 that was closed prematurely regarding this problem 🙁

[lukehoban]

There isn't a repro here to validate against, but I am fairly confident this is ultimately one of the three issues noted in #920 (comment), so closing as a duplicate of those.