This message was deleted.

Sorry if I'm tagging a wrong person @steep-sunset-89396, maybe you could advise on the above?

I am not sure what is your goal. If you are trying to create stacks dynamically or only resources/components? For resources, you'd create Component Resources and then share them as a library/package. Should you need to create pulumi stacks dynamically, you can use

pulumi cli

or automation API for more control.

If you’re truly looking for templates, you can totally create your own templates that will be consumed by

pulumi new

. A little-known fact is that

pulumi new

supports passing a path or URL to a template in order to use that template when creating the new project. This blog post talks a bit more about the process: https://www.pulumi.com/blog/how-to-create-and-share-a-pulumi-template/ Does that help?

Good morning! @great-sunset-355 thank you for suggestions! My goal is to: • dynamically create stacks and components • keep as less reusable code and settings in services repositories (keep the reusable code and settings separately) Thank you @salmon-account-74572 for the articles on templates, this is very close to what I need! Let me experiment with this.

@narrow-needle-95047 If you have additional questions about templates, feel free to hit me up.