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, is there a canonical way  to emit a warning log message whenever a particular resource has been created?

possibly printing values of some outputs of this resource

<https://www.pulumi.com/docs/intro/concepts/logging/>

<@U013Q0AKUCW> thanks, but this:
```// Used by this Pulumi program for updates
const pulumiUp = new opsgenie.ApiIntegration("infrastructure/opsgenie pulumi up", {
    allowWriteAccess: true,
    type: "API",
}, {
    aliases: [{
        name: "infrastructure/opsgenie Pulumi provider",
    }],
})

pulumi.log.warn(
    pulumi.interpolate `${pulumiUp.name} key has been exposed, please rotate it at <https://taxamo.app.opsgenie.com/settings/integration/edit/API/${pulumiUp.id}>`, // this is line 30
    pulumiUp
)```
causes this:

```integrations.ts(31,5): error TS2345: Argument of type 'Output&lt;string&gt;' is not assignable to parameter of type 'string'.```

`pulumiUp.apply(v =&gt; { pulumi.log.warn(v.id); });`

<@U013Q0AKUCW> aaah, very nice :slightly_smiling_face:. Any idea how to check if the resource has just been created?

The resource should be created if you're inside the apply.

I'm curious if you're trying to setup an SNS topic subscription to OpsGenie?

nope, I am trying to set up Opsgenie API keys to be used with Pulumi in CICD

<https://pulumi-community.slack.com/archives/C84L4E3N1/p1627916176046500?thread_ts=1627915428.043900&amp;cid=C84L4E3N1> - yeah, but I need this warning not to appear in subsequent runs when the resource already exists

`${pulumiUp.name} key has been exposed,` are you trying to work around the fact that this output exposes a secret?

<@U013Q0AKUCW> I am using separate API keys for pulumi preview (because it can be ran from any branch) and for pulumi apply (because it can be ran only from the master) and I need to make it impossible to retrieve the pulumi update API key when running a pulumi preview

You might just want `additionalSecretOutputs` in opts

otherwise anybody pushing to a non-master branch can push a  CI job that will print the pulumi up API key

when using `additionalSecretOutputs` it should mask secrets when printed.  However, if the user has access to retrieve secrets, then they can definitely retrieve the value :slightly_smiling_face:

You might be bleeding into Dynamic Resource Providers if you need to tap into the lifecycle hooks of a resource <https://www.pulumi.com/blog/dynamic-providers/>

alternatively I could just override the value of the `apiKey` attribute of the resource with 'undefined' if there was a way to do it