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

I'm not aware of a best practice. If I was doing this, I'd probably consider wrapping the build and pulumi app in a sinlgle script, rather than putting the build into the deploy. I'd be worried about sharing node_modules accidentally, using wrong versions of dependencies, etc.

I am using pulumi only to deploy infrastructure (s3 in this case) and I use circleci for building the client and pushing it to the s3 bucket

you can use aws circleci orb for that, it's pretty easy

```- run:
    name: Deploy to S3
    command: |
      aws s3 sync dist/client s3://${S3_SITE_BUCKET_NAME} --no-progress --delete```

Not sure if running it as part of the pulumi deploy would be a good idea, but you should be able to do it using Dynamic Resource Providers.

There is an example that may be useful to adapt - <https://github.com/pulumi/examples/tree/master/aws-ts-ec2-provisioners>.

Likely to much more work that just doing it as a build step or wrapper script though...

<@U01RXLSUER5> the default way, when using Pulumi, is that Pulumi invokes `node` to create the needed resources. If you want to drive Pulumi from within your NodeJS code, have a look a the Automation API. In that setup, the Pulumi engine will be started by your NodeJS code and you can programmatically set the environment, stack config, etc.
<https://www.pulumi.com/docs/guides/automation-api/>

Thank you all!

&gt; wrapping the build and pulumi app in a sinlgle script,
This is what we are doing now. The problem is that the API endpoints are generated in other pulumi projects, they are not accessible when building the REACT application. <@U012UJTT55M> <@U02L1UHTLJ3>

&gt; use circleci for building the client and pushing it to the s3 bucket
CI/CD works, But we don't have CI/CD setup for every stack. <@U01JBAPC4P7>

&gt; Pulumi invokes `node` to create the needed resources.
This is what I am thinking to give it a try. Thank you for sharing the other way of driving Pulumi from within NodeJS code using the Automation API. :+1:  <@UK4HNFLCB>