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

Hi <@U015NLXAHM1>

Can you get some indication from the pulumi up (via the details view) of what is changing in there?

Hi <@UHTP242EB> I’m not sure what you mean by details view but I ran `pulumi up --yes --debug`  and it dumped a lot of stuff at me.  What should I be looking for? Thanks

when you run `pulumi up` without `--yes` it will ask `yes / no /details`

the details view will tell you what it is doing

Ah ok, got you now.  It just says the viewerCertificate is different even though it has not changed.

```     Type                            Name     Plan       Info
     pulumi:pulumi:Stack             cli-dev
 ~   ├─ aws:cloudfront:Distribution  cdn      update     [diff: ~viewerCertificate]
 ~   └─ aws:route53:Record           get-dev  update     [diff: ~aliases]```
The route53 record depends on the cloudfront distro so that’s expected

So the issue here is that aliases are a non-deterministic order :confused: This is abug in the upstream TF provider that we are desperate for a fix for...

Of course, that's no excuse - but ow we know what the issue is

if the record rarely changes, then you can use ignoreChanges on the aliases and it will stop that perpetual diff

Hi <@UHTP242EB> I tried commenting out the Alias and running the program (so it deletes the alias) and then re-running to see if the problem I originally asked about with the cloudfront distro goes away and I found it’s not made any difference.

```❯ pulumi up
Previewing update (dev):
     Type                            Name     Plan       Info
     pulumi:pulumi:Stack             cli-dev
 ~   └─ aws:cloudfront:Distribution  cdn      update     [diff: ~viewerCertificate]

Resources:
    ~ 1 to update
    11 unchanged```


That’s the full output and the cert has not changed.

```  pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:dev::cli::pulumi:pulumi:Stack::cli-dev]
    ~ aws:cloudfront/distribution:Distribution: (update)
        [id=E3FUPHGDNK3CR3]
        [urn=urn:pulumi:dev::cli::aws:cloudfront/distribution:Distribution::cdn]
        [provider=urn:pulumi:dev::cli::pulumi:providers:aws::default_2_13_0::8beca890-e310-4e01-92db-d9ade05b9fd9]
      ~ viewerCertificate: {
          ~ cloudfrontDefaultCertificate: false =&gt; true
        }```


And in the details what’s the diff about the viewer cert? Anything obvious?

Yeah that is the issue - looks like we have a default that isn’t being set back to state...

Are there any github issues I can look at so I can understand the problem a bit better?