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

All the languages support shelling out and run external commands, so that's one option. The downside is that you have to build you own logic regarding if you need to run the scripts or not.

Pardon me because I'm missing the correct terminology, but with a custom provider/custom resource you can have Pulumi do that for you and also deal with diffs.

There is an open issue to support this out of the box: <https://github.com/pulumi/pulumi/issues/99> but this comment should get you started for now: <https://github.com/pulumi/pulumi/issues/99#issuecomment-737429204>

<@U013QM2EK7Y> thank you very much… i think that will build custom dynamic provisioner in the future for sure, for now putting some logic on CI side before running pulumi up is somewhat of an acceptable solution… can move this part to K8s jobs as well, a lot of options :slightly_smiling_face:

Thanks <@U01EPRHN6HF> will check them out, especially the `aws-ts-ec2-provisioners` one