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

datadog.ts

There's some code missing. Where are you calling `createDataDogIntegration()` from? If that's in an `apply()` then you'll see this behaviour. Does it actually deploy new resources? I'd guess it won't: it just can't tell at preview time that the before and after values are the same, so it shows that there's a potential difference.

That said, I've never used the _aws.cloudformation_ API, so maybe it does work that way? It might be worth converting the CF stack to Pulumi.

Aside: `accountId: pulumi.all([current]).apply(([c]) =&gt; c.accountId)` is exactly the same as `accountId: current.accountId`.

going to quote the docs here:
<https://www.pulumi.com/docs/intro/concepts/inputs-outputs/>

&gt; During some program executions, apply doesn’t run. For example, it won’t run during a preview, when resource output values may be unknown. Therefore, you should avoid side-effects within the callbacks. For this reason, you should not allocate new resources inside of your callbacks either, as it could lead to pulumi preview being wrong.
