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

Sounds like a good use for our `ComponentResource` model: <https://www.pulumi.com/docs/intro/concepts/programming-model/#authoring-a-new-component>

Don't forget that you can share these (and a lot of the code you write) in the same way you'd share other such libraries: npm, nuget, pip etc

Thanks Piers.. would the general strategy be to create a new 'stack' for each environment then? and effectively put the 'reusable' template stuff into a component?

<@U01FHRQA2Q7>

Yeah a "stack" is just a representation of the state and config for a collection of resources so a stack per env or even a stack per developer is the general use here

I have seen people using a stack per customer tenant as well but YMMV

ok, thanks Paul... makes sense, cheers. would we need a separate little 'program' per stack? in .net , it generally goes

```class Program
{
    static Task&lt;int&gt; Main() =&gt; Deployment.RunAsync&lt;MyStack&gt;();
}```


nope - MyStack is a generic class used so dev1 stack will use MyStack, dev2 stack will use MyStack

MyStack probably should be named MyProject

So let’s say we renamed MyStack to MyProject. 

_how_ would dev1 stack use MyProject? Sorry if it’s a dumb question, just trying to join the dots. Would it inherit from it? Would it new it up? 

So let’s say your application creates a resource group, a storage account and a storage container

A stack is when you deploy that project - let’s say to a dev environment

So the stack is just the actual state of the resources (+ any config) 

Stacks are the deployed resources on top of a project

Hmm. Kind of. 

So you’re saying that the project is like the blueprint. And the stack is like the result of constructing based on that blueprint. 

So I guess I’m wondering how to organise the code so that I can construct that blueprint several times (with slightly different configurations) within one account. 

You don’t need anything special for that

Create your code then

 &lt;for each name in a loop&gt;
Pulumi stack init

That will create you all the stacks you need on top of the project and then you can add config and run Pulumi up in each of those stacks independently 

A project (where your code resources live) can have many stacks (pointing to where the resources have been deployed)

Each stack can take its own credentials and config and the base code will be deployed as the stack dictates

Thanks very much Paul for taking the time to explain to me.  I don’t suppose there are any examples I could refer to?

There’s a small intro as code workshop you can step through 

This should help you with the Pulumi concepts <https://github.com/pulumi/infrastructure-as-code-workshop/blob/master/labs/aws/csharp/README.md|https://github.com/pulumi/infrastructure-as-code-workshop/blob/master/labs/aws/csharp/README.md>

Ping me if you need anything - happy to help!