Skip to content

Conversation

@SharpEdgeMarshall
Copy link

@SharpEdgeMarshall SharpEdgeMarshall commented Mar 28, 2025

This PR adds support to workspaces that contain multiple nested Pulumi projects.
It generates multiple launch configurations for each Pulumi project found inside the workspace folders (even nested ones).

Co-authored by: @mbovo

@SharpEdgeMarshall SharpEdgeMarshall force-pushed the add-support-for-multi-project-folder branch from 60c0312 to 4d5ec09 Compare March 28, 2025 14:49
@SharpEdgeMarshall SharpEdgeMarshall changed the title Add Support for multiple projects in a folder Add Support for multiple projects in a workspace Mar 28, 2025
@EronWright
Copy link
Collaborator

EronWright commented May 23, 2025

Thanks @SharpEdgeMarshall for the contribution!

I wasn't sure about the performance implications, e.g. in the face of a node_modules directory. And I would like to ensure that the launch configuration name is simple and clear, especially in the simple case of a root-level project. I'll take this for a spin, e.g. against the pulumi-examples repository.

I'm curious whether you find the alternative solution - "Add Folder to Workspace..." - to be inconvenient.

@EronWright EronWright self-assigned this May 23, 2025
@SharpEdgeMarshall
Copy link
Author

SharpEdgeMarshall commented May 26, 2025

Hi @EronWright, the problem with "add folder to workspace" is that we handle hundreds of pulumi projects, so having to add them individually is a bit messy.
We have "groups" of pulumi projects that shares the same .venv and we create a workspace root dir for each one of them.

@EronWright
Copy link
Collaborator

@SharpEdgeMarshall that's reasonable. Let me point out that, aside from the "automatic" debug configurations, you can also create launch configurations by hand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants