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

btw just to alleviate any confusion about how automation API currently functions -

The automation API currently has a hard dependency on the CLI. And the CLI requires a pulumi project directory - meaning it requires a pulumi.yaml.

When you construct a local workspace, if you provide a `WorkingDirectory` than the automation API will assume that directory already has pulumi YAML files in it and try to operate using those.

If you _do not_ provide a `WorkingDirectory` than the automation API creates a temp folder and generates a pulumi YAML in this temp directory that it will then be working out of until disposed.

If you pass any values into `ProjectSettings` than those values will be serialized into the pulumi YAML file that it uses. If you pass any values in the `StackSettings` collection than it will serialize each instance into a pulumi stack YAML file.

The issue you had with the project name sounds interesting - I am curious what the actual value of the project name was in your scenario. Like if you looked at the generated temp folder (you can find it by looking at the `WorkingDirectory` property on the local workspace) and examined the project name that it had serialized into the YAML file, would the value be `roomote-cal-sync`?