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

:seedling:  Bazel &amp; Pulumi :seedling:

I’m looking for feedback on using <https://bazel.build/|Bazel> (or <https://buck.build/|Buck>, <https://www.pantsbuild.org/|Pants>, <https://please.build|Please>) as a build system together with Pulumi

Has anybody had success with it ?

Is it possible to integrate Pulumi in the overall build process or is it always a separate binary that needs to be managed on its own ?

Is it possible to prevent unnecessary `pulumi up` when dependencies haven’t changed much ?

If nothing has changed, Pulumi up should report no changes anyway, so it should be harmless to run it frequently. IOW, assuming Bazel is similar to make, Pulumi itself is keeping track of the dependencies, so you should just run it every time in most circumstances.

If there's some context I'm missing, can you provide more details about the problem you might be seeing?

Bazel can perform multi language builds 

Pulumi is one language at a time and doesn't build applications 

Bazel has better docker layer management than Pulumi docker (in theory)

Have you looked at the Automation API? It might be a better fit for what you want. It would allow you to build a Pulumi program using Bazel because you embed Pulumi _in_ a regular program and can call it without the Pulumi CLI.

Some hopefully helpful links:
• <https://www.pulumi.com/docs/guides/automation-api/>
• Python sample code: <https://github.com/pulumi/automation-api-examples/blob/main/python/inline_program/main.py>