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

Might not be a change, might be a default value? That message says "it was unknown, now it's known to be empty".

Yup, thanks!

I'm not sure why it wasn't initialised to an empty string when the resource was first created.

Have you done a `pulumi refresh` recently?

It's the refresh that's causing the issue with the automation api. `stack.refresh(expect_no_changes=True)` will throw an error if there's a diff

I've never been able to get expectNoChanges to work, at least not without
1. upping,
2. refreshing with no changes,
3. previewing and noting all the new differences, and
4. updating the code to eliminate the differences.

I find that there's always differences between unset values and defaults, at least in the AWS resources...

Just on this, <https://github.com/pulumi/pulumi/issues/3569#issuecomment-568233415> (Older comment but I think its true) so,
ignore_changes flag will not be used when the refreshing.