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

&gt; then they can press a button to spin up a new instance in their DO account and with all the configuration and software installed.
I think the Pulumi Automation API (C# version fore xample (<https://www.pulumi.com/blog/automation-api-dotnet/>)) could help with this, it can be used for managing Pulumi projects, basically
it wraps the `pulumi` CLI in a software library for each of Pulumi's supported language.

You define the Pulumi `Stacks` yourself with the necessary DO resources,
then make the stacks configurable using pulumis configuration.

Use the automation API in your API Endpoint to manage stacks (update, destroy).

I know the DigitalOcean provider can be used with setting `digitalocean:token` variable in the Pulumi config,
setting the variable as `--secret` ensures the variable is encrypted so it can be stored safely.

Maybe for example using the username or something as the Pulumi stack name, or some other user related field. The automation API allows you to select the name of the stack you are working with, so in your API endpoint you just need to get the current user to manage their Pulumi stack.

Thank you, <@U01R1NV536E> Is tehre a python equivalent of the automation API?

Yeah, <https://www.pulumi.com/blog/automation-api-python/>
and examples <https://github.com/pulumi/automation-api-examples>