Add some real examples?

[antstanley]

File: themes/default/content/docs/guides/organizing-projects-stacks/_index.md

Currently trying to figure out a strategy for handling projects/stacks, but the example you specify in this just goes to another set of docs. Please can you add some viable examples on ways to handle projects/stacks, in particular for my use case, an example of projects and stacks where multiple services exist in a monorepo

[susanev]

hi @antstanley thx for opening an issue! some folks are working on example content for that page right now.
feel free to take a look at the pr and let us know if this will address your need.

pulumi/pulumi-hugo#1124

[mattstratton]

in particular for my use case, an example of projects and stacks where multiple services exist in a monorepo

that's a bit of what I was going for in that PR; as @susanev said, I welcome your thoughts as I update it!

[antstanley]

Hey folks! Thanks for getting back to me. So what I'm looking at doing is something like this.

monorepo-root
├── services/
│   ├── service A/
│   │   ├── infrastructure/
│   │   │   └── index.ts
│   │   ├── src/
│   │   │   └── app/
│   │   │       ├── index.ts
│   │   │       └── etc...
│   │   ├── Pulumi.staging.yaml
│   │   ├── Pulumi.production.yaml
│   │   ├── Pulumi.yaml
│   │   ├── package.json
│   │   └── tsconfig.json
│   ├── service B/
│   │   ├── infrastructure/
│   │   │   └── index.ts
│   │   ├── src/
│   │   │   └── app/
│   │   │       ├── index.ts
│   │   │       └── etc...
│   │   ├── Pulumi.staging.yaml
│   │   ├── Pulumi.production.yaml
│   │   ├── Pulumi.yaml
│   │   ├── package.json
│   │   └── tsconfig.json
│   ├── service C/
│   │   ├── infrastructure/
│   │   │   └── main.go
│   │   ├── src/
│   │   │   └── app/
│   │   │       ├── app.go
│   │   │       └── etc...
│   │   ├── Pulumi.staging.yaml
│   │   ├── Pulumi.production.yaml
│   │   └── Pulumi.yaml
├── .gitignore
├── node_modules
├── package.json
├── pnpm-lock.yaml
├── pnpm-workspace.yaml
└── tsconfig.json 

I have a monorepo, using pnpm to manage it. Each service is distinct from each other with no dependencies between them. They need to be deployed independently of each other, with their own stacks (ie staging/production etc). There is also potential for mixed languages in the repo, as some services might be written in TypeScript, Go or Python, though each service should only use one language. I've got a CI pipeline using CircleCI that is triggered on every commit to the Github repo that has some logic built in to figure out which service to deploy and which stack.

From a Pulumi perspective, how do I configure this? Is it a project per service, vs a project for the repo? Do I need a Pulumi.yaml in the root of the monorepo?