I'm new to Pulumi, and am trying to use it as an "automation" type thing within a .net core web app. I found the "inline" code examples, but here is basically what I want. I have a basic default web page, with two buttons. Create, and Destroy. When I hit create, I want it to simply create a new VPC (my aws sso creds are current). When I click destroy, it should destroy said VPC. I have pulumi installed, aws cli installed, and of course .net stalled. Using visual studio at the moment. It is trying to say "pulumi" can't be found when debugging.

{"An error occurred trying to start process 'pulumi' with working directory '<project directory>'. The system cannot find the file specified."}

The

pulumi

CLI command has to be available in the environment you're running your code because the Automation API is calling out to the CLI. It looks like the command is not in the

$PATH

of your debug session in VS Code.

Hmm...I'm using Visual Studio IDE, not VS Code and on Windows I see the pulumi path is in the "system" path setting, so in theory..it should be in the path regardless....

Yes, the IDE doesn't matter. It could also be that Pulumi cannot find the files or your project directory. "The system cannot find the file specified." doesn't seem to come from Pulumi.

Fixed that part..had to close all instances of VS.

Yes, in two ways: Either you use the AWS default provider, in which case you can do it via the terminal environment: https://www.pulumi.com/registry/packages/aws/installation-configuration/#aws-installation-configuration

Perfect

Canonically, you would give each user their own stack, based on the same program.

K. That should be easy enough. So its "stack" based. Thanks!! That should be enough to get me rolling down this hill...

You can also give each user their own project and the same set of stacks, which is sometimes more aligned with the overall structure of your application, but this is orthogonal to the way Pulumi is designed

Ya, in short, I need to provide a way for a limited set of users to create AWS Ec2's based on a name they provide. So it auto-tags/creates vpc, subnet, security group, ec2 (with same base tags). everything would be named like <company>-prod-<name>-resourcetype-<etc>

Yes, I'd say especially if you just have one stack per user, keep everything in one project

If I'm configuring that inline, I would assume its another SetConfigValue, and then setting pulumiautonamingpattern...but i'm not entirely sure that is now "nested" config works inline

Not sure I ever had to do this, but have a look at https://github.com/pulumi/pulumi/issues/5506#issuecomment-703765944