This message was deleted.

sorry didnt see self-reference, not sure if you can do that

In general no - this is not possible.

i have an issue where I'm trying to write a JSON setting to a AWS DMS ReplicationTask's

replicationTaskSettings

property:

{
  "Logging": {
    "LoggingEnabled": true
  }
}

https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/dms/#ReplicationTaskArgs-replicationTaskSettings The problem is that the default setting (which is kept in JSON format in AWS) contains a lot of default values, which get merged with the JSON document I submit to turn on logging. As a result, every time i

pulumi up

it looks like the values have diverged, so i get an 'update' operation every time. To copy all the default values into the JSON document I submit, with logging turned on of course, I need to know the task's ARN — one of the settings is

CloudWatchLogStream

who's default value is

"dms-task-<the ARN of the task>

. I'm trying to figure out the best way to deal with this. Any ideas?

I actually have some code doing all of this for an internal tool. It is indeed a bit painful due to how DMS works here. I ended up explicitly including the full JSON in our code to fully specify this - and marked it up with comments about where things diverge from defaults. For the log stream, I ended up doing a

refresh

and then hard-coding in the resulting value. This makes it a little harder to stand up from scratch correctly, but provides a way to close the loop for an existing deployment. You can also consider using

ignoreChanges

to ignore any perceived changes in these settings.

cc @dazzling-memory-8548 ☝️

Depending on exactly how you are relying on it - yes 2936 may be required before this would fully suppress the diff.

i'm just adding

ignoreChanges: ["replicationTaskSettings"]

to the aws.dms.ReplicationTask resource. I wrote a custom resource to take care of the settings and manage the diff properly, but it's not fixing the problem since ignoreChanges isn't working and ReplicationTask continues to want to re-write the settings value.

How do i peg my npm dependency to pulumi master

You can use

"@pulumi/pulumi": "dev"

to pin to the dev tag which is the latest

master

build.

Thanks! That works, but I'm realizing that the ignoreChanges fix is more about the CLI than the node library.

I believe the improvements to

ignoreChanges

need to be brought into providers as well before you'll see a change. I think that is still in progress. Which provider in particular are you interested in?

aws

This is pending https://github.com/pulumi/pulumi-terraform/pull/441, which will then need to get picked up by an AWS provider release.

quite the daisy chain! 🤪 ok, thanks for the info, Luke