https://pulumi.com logo
#aws
Title
# aws
p

purple-appointment-84502

06/29/2021, 2:19 AM
Hi all, getting some strange updates/diff when running pulumi refresh that includes some RouteTableAssociations
gatewayId : undefined => ""
I'm using the automation api and the
expect_no_changes
flag which causes an error. Any idea what causes these properties changes? Thanks!
l

little-cartoon-10569

06/29/2021, 2:48 AM
Might not be a change, might be a default value? That message says "it was unknown, now it's known to be empty".
p

purple-appointment-84502

06/29/2021, 2:55 AM
Yup, thanks! I'm not sure why it wasn't initialised to an empty string when the resource was first created.
l

little-cartoon-10569

06/29/2021, 2:55 AM
Have you done a
pulumi refresh
recently?
That often causes that sort of thing.
p

purple-appointment-84502

06/29/2021, 3:00 AM
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
l

little-cartoon-10569

06/29/2021, 3:10 AM
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.
👍 1
I find that there's always differences between unset values and defaults, at least in the AWS resources...
👍 1
p

purple-appointment-84502

06/29/2021, 3:35 AM
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.
4 Views