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

This appears to be what I want, I’ll try to hack around with a node script executed from the `local.Command` and see if I get the right lifecycle (after deployment rollout)

<https://github.com/pulumi/pulumi-command/issues/7>

Command is definitely an option here, but you can likely run that typescript function inside an apply 

<@UCWG26BH7> this is a bit hacky but what I came up with since we cannot run direct functions/callbacks:

```import { Web } from '@alienfast/pulumi-app'
import { local } from '@pulumi/command'
import { unsecret } from '@pulumi/pulumi'

import { apiKey, email, zoneId } from './cloudflare'
import { rules } from './pageRules'

export function purgeCache(web: Web) {
  const cmd =
    'node --experimental-specifier-resolution=node --loader ts-node/esm --no-warnings src/cmdPurgeCache.ts'

  const urls = Object.keys(rules)
  unsecret(apiKey).apply((key) =&gt; {
    const cmdPurgeCache = new local.Command(
      'cmdPurgeCache',
      {
        create: cmd,
        update: cmd,
        environment: {
          'trigger-update': new Date().toISOString(),
          EMAIL: email,
          KEY: key,
          ZONE_ID: zoneId,
          URLS: urls.join(','),
        },
      },
      {
        dependsOn: [web],
      },
    )
  })
}```

I had to hack the
```environment: {
          'trigger-update': new Date().toISOString(),```

One thing though, I would really like to see my console output, and I cannot see the results of the command execution.  This makes it quite difficult to write/debug something like this

I do see the output in ci via `pulumi up -y --non-interactive --skip-preview`