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

<@UG77VR58X> 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?

Untitled

AWS is scheduling this change for Wednesday

Screen Shot 2019-08-05 at 8.12.58 AM.png

Here's a screenshot from AWS console after I run pulumi up

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?

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

ok, so maybe I can't see what the issue is - do you want it to happen straight away?

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

I would expect that to be the case, I understand that pulumi will continually throw diffs on this

what do folks usually do to mark changes that are pending?

so in this specific case, until you know it changes, you can use ignoreChanges

it looks like the only other option would be to set `applyImmediately` to true

yeah that's the path of most resistance :smile:

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.