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

AFAIK no, which is one of the reasons why we moved away from YAML and use Python

YAML is elegant in that it’s fast and language-agnostic... but it’s definitely not made for larger projects IMO

I think I'll try microstacks approach so it will limit amount of configuration in single yaml file. But it would be great to have an option to use multiple yaml files

If you go for many stacks, then you’ll have to run many “pulumi up”... unless you intend to use Pulumi Automation to script that and run them sequentially somehow ?

Multiple gitlab-ci.yml files, one per folder which handle pulumi up for single service.

For YAML there is the option to run a command that produces the YAML file, which for example could be used with other tools such as CUE to combine multiple files into a single YAML.

<https://leebriggs.co.uk/blog/2022/05/04/deploying-kubernetes-clusters-in-absurd-languages>

Hm, when using "mono" stack I had stack per env in project. But going with microstack I need to use tags `env:dev` But how to handle configuration file with that approach. I had Pulumi.dev.yaml and Pulumi was just getting config from this file when given stack was selected.

Ah nevermind, Pulumi is grouping them by Gitlab repo, neat

Cool article <@UK4HNFLCB>

I laughed when I saw good ol' Fortran in there :laughing:

Basically, the `compiler` parameter allows you to pre-compile your YAML with any language (I would use Python instead of Fortran... but eh)

Doesn't that kinda defeat the purpose of using YAML in the first place ?

Maybe that makes sense to do it if all the compiler does is regroup a bunch of files into one big YAML, idk