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 use inline programs in Go mainly because of the ability to bundle everything as a binary (example: <https://github.com/jaxxstorm/connectme>)
For anything that doesn’t need a bundled binary I use local programs

That's a great point!! Thanks for your response :+1:

Is there a specific reason you don't use inline programs for non-binary bundle use cases? Prefer the isomorphic approach/portability of the projects, like the Pulumi manifest config control, etc.

I guess 1 benefit of *not* using inline programs is that you can drive that program using either automation API *or* the CLI - whereas with inline programs you can only use automation API to execute them

That being said, when I've used automation API for projects I've almost exclusively used inline programs just for simplicity and ease.

Awesome <@U01038HJ93R>, thanks for your input. That's what I was thinking too. No joke, almost DM'd you with your deep experience of the automation API haha. Thanks for all the work you put into it/the automation examples/etc.!

Thanks for the kind words <@U045282JBNY>!

It is possible to have the best of both worlds with a little bit of refactoring. We don't have an example of this for nodejs, but here is a program in go that can be run both via the CLI and via inline program:

<https://github.com/pulumi/automation-api-examples/tree/main/go/inline_local_hybrid>

Thanks <@UQ8K13T7X>! I was originally doing that with my current project since I couldn't decide between the two, now switched to pure inline programs. The Go examples have been very helpful and I love how flexible the automation API is/how many ways you can go about it