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

Seems like this template section of the Pulumi.yaml is just for pulumi new, but creates a new project as well.

There's a --generate-only option, but it skips the stack  not the project :disappointed:

Do you have a link to the docs on the "template for configuration defaults"? Do you mean the `config:` section of Pulumi.yaml?

```name: base
runtime: nodejs
description: The infrastructure base, includes DB, Service Account, and certificate configuration.
template:
  description: Environment stack for utilize the base infra project.
  config:
    gcp:project:
      description: The GCP Project for this stack.
      default: prime-dev-374422
    region:
      description: The GCP region for which to deploy, this get's inherited by stacks further down the tree.
      default: us-east4
      secret: false```

<https://www.pulumi.com/docs/reference/project-file/>

Yea that doc does imply that `new` is the only way to go, and `new` isn't really for stacks. Confusing. I think the docs need more examples.

Still, you should be able to get `pulumi new` to create a stack in the current project. Have you used the `--stack` option?

Pulumi new always clobbers the existing directory. And --stack just specifies the name for the stack instead of being prompted.

I ended up just creating a dummy stack that has some default config set then using `pulumi stack init --copy-config-from`

Not the most elegant solution, but it works.

Good that it works. You should raise an issue about the `template:` project option. It sounds like it needs better docs (like not saying it works with `pulumi new`), and it needs to work with `stack init`.