https://pulumi.com logo
#general
Title
# general
w

worried-engineer-33884

08/05/2019, 11:59 AM
With the new strategy to push diff logic down to the provider and query the backend for old state, I am encountering a case where certain DMS replication instance changes are continuously trying to "update" because AWS schedules the changes during a maintenance window—which can be several days out. Is there a suggested strategy for this kind of scenario so that Pulumi does not continuously try to update the same parameters?
b

broad-dog-22463

08/05/2019, 12:07 PM
@worried-engineer-33884 can you run
pulumi up
and grab the details view for me and post it here and we can work out what the problem is?
w

worried-engineer-33884

08/05/2019, 12:11 PM
Hi Paul, here's the pertinent piece.
AWS is scheduling this change for Wednesday
Here's a screenshot from AWS console after I run pulumi up
b

broad-dog-22463

08/05/2019, 12:16 PM
ah, so in this case, if this has been changed in AWS, outside of Pulumi, then you need to
pulumi refresh
and have a look at the details of what it will do
can you have a look at that and output it here?
w

worried-engineer-33884

08/05/2019, 12:17 PM
it wasn't changed in AWS — i changed it in pulumi — but AWS does not change the replication instance size right away, it is scheduled
b

broad-dog-22463

08/05/2019, 12:17 PM
ok, so maybe I can't see what the issue is - do you want it to happen straight away?
w

worried-engineer-33884

08/05/2019, 12:18 PM
not necessarily, the issue is that subsequent runs of
pulumi up
continue to try to modify this value because AWS has not performed the change yet
b

broad-dog-22463

08/05/2019, 12:18 PM
that's kind of expected TBH
Ok, let me rephrase that
I would expect that to be the case, I understand that pulumi will continually throw diffs on this
FWIW, Terraform does the same AFAICR
w

worried-engineer-33884

08/05/2019, 12:20 PM
what do folks usually do to mark changes that are pending?
b

broad-dog-22463

08/05/2019, 12:25 PM
so in this specific case, until you know it changes, you can use ignoreChanges
w

worried-engineer-33884

08/05/2019, 12:27 PM
ok
it looks like the only other option would be to set
applyImmediately
to true
b

broad-dog-22463

08/05/2019, 12:34 PM
yeah that's the path of most resistance 😄
🤪 1
w

white-balloon-205

08/05/2019, 3:13 PM
Or
ignoreChanges
?
w

worried-engineer-33884

08/05/2019, 3:15 PM
ignoreChanges would have to be toggled when we actually do want to change this resource. That doesn't jive too well with our ci/cd workflow, although the changes to a replication instance should be few and far between.