No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Is anyone familiar with the intricacies of lambdas and pulumi resolving changes/getting false dirties? <https://pulumi-community.slack.com/archives/C84L4E3N1/p1741131144654509>

I realized it really is somewhere in the lambda as even with `ignore_changes=["code"],` on something that was showing an infinite `[diff: ~code]` on every `up`, I now see `Plan` =&gt; `update` with no `Info` and a `~ aws:lambda/function:Function: (update)` in the diff without any other differences listed… a phantom diff!

image.png

Wait… holy crap… so I added `ignore_changes=["*"],` to my options and for some reason on my next run I got:

```aws:lambda:Function                  my-lambda                     2 errors

...

Diagnostics:

...

aws:lambda:Function (my-lambda):
    error: aws:lambda/function:Function resource 'my-lambda' has a problem: expected application_log_level to be one of ["TRACE" "DEBUG" "INFO" "WARN" "ERROR" "FATAL"], got . Examine values at 'my-lambda.loggingConfig.applicationLogLevel'.
    error: aws:lambda/function:Function resource 'my-lambda' has a problem: expected system_log_level to be one of ["DEBUG" "INFO" "WARN"], got . Examine values at 'my-lambda.loggingConfig.systemLogLevel'.```
As if somehow that had previously been suppressed by the erroneous diffs… I then added those two parameters, removed the ignore, and ran up again and the diff went away

This worked for the lambda with the `aws.lambda_.Invocation` + docker image… but it did not work for my `[diff: ~code]` lambda

Ahh right, this one, <@U076R8HUSSU> kindly reminded me is related to this: <https://github.com/pulumi/pulumi/issues/17792>