the problem I’m having is the following.. I’m building the React app before deploying with pulumi.. but… my React app code relies on a Amazon Cognito User Pool Client ID… therefore, on first deploy, the infra needs to be deployed, and only then the react app can be built / deployed, because only then I can pass the client ID to my react app as an env variable

note that, in React world, env vars values are actually baked into the built code.. which is different from, say, Lambda fns, which can have env var values sent via its Environment Variables option, and they are fetched in runtime

all in all, in an ideal scenario… the first deploy should go like 1. deploy user pool client 2. build the app (user pool client ID is correctly baked into the app code) 3. proceed with deploying the app and other resources

BTW React app is hosted on S3.. so yeah, a bucket deployment will also happen before the React app build is uploaded to it.. but yeah, no worries here, all works fine (because the React app code doesn’t rely on a S3 bucket balue, for example its ID or public URL)

The S3 bucket for example, is that bucket going to be used for any other purpose. You might be able to pull the management of the bucket into a shared infra project as it has a different lifecycle than the application you are deploying and the bucket might not need to be created by the app deployment

at the moment, S3 is really not an issue, only the fact that the React app is being built before being deployed, where deployment includes the user pool, on which the React application depends..

so, it’s like: 1. react app build 2. new user pool client deploy 3. react app deploy to s3

but it should be

1. new user pool client deploy 2. react app build 3. react app deploy to s3

the build needs to happen during the deployment, and that was the reasoning behind the question I initially asked:

anybody maybe managed to embed the build step into the Pulumi (TS) code maybe?