This message was deleted.

sparse-intern-71089

08/10/2023, 4:56 PM

This message was deleted.

acceptable-chef-92575

08/10/2023, 5:16 PM

Followup question, using s3 backend, when does size of state start to become an issue? if at all?

salmon-account-74572

08/10/2023, 5:26 PM

From a Pulumi perspective, I would say that #2 is probably the best approach. It’s true that “Pulumi project ~= folder”. This doesn’t preclude you from factoring out common code and re-using that common code across all the Pulumi projects (i.e., putting common code into a

imports

directory or the like and then importing into each Pulumi program as applicable/needed). As for state, I don’t know the answer to any size that might generate a concern, but each stack (an instance of a Pulumi project) will have its own state. Since you are separating things into separate projects/folders, then you’ll have separate stacks and therefore separate state files.

salmon-account-74572

08/10/2023, 5:26 PM

You might also find some of the recommendations in this series helpful: https://www.pulumi.com/blog/iac-recommended-practices-code-organization-and-stacks/

acceptable-chef-92575

08/10/2023, 7:00 PM

salmon-account-74572

08/10/2023, 7:03 PM

NP! Let us know if we can help further.

Open in Slack

Previous Next

Pulumi Community

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.