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

<@U05H1AM1M3M> perhaps you could extract all the common configs in a project level config and use stack configs for whats left?
<https://www.pulumi.com/blog/project-config-mvp/|https://www.pulumi.com/blog/project-config-mvp/>

there is no common config
I have a stack of keycloak
It have many clients, roles
A lot of users + role mapping

keycloak has its own config export/import mechanism, maybe leverage that   ( or write a Keycloak Provider :smiley: )

<https://github.com/pulumi/pulumi-keycloak>

User don't need to edit python code for every new user role mapping
I use a for loop over CONFIG to do that
So the question only is `is there a good way to split config?`

I has decised to store config in many yaml, then use pyyaml to load it

<@U05H1AM1M3M> in your case I believe this is a good approach. I assume each stack is a standalone version of the setup for each user, correct?

hmm, I only have one keycloak stack
other stack is used for different purpose

So I the method I was using utilized `spruce`
./spruce.sh
```spruce merge accounts/*.yaml sso_permission_sets/*.yaml templates/*.yaml sso/*.yaml```
e.g. accounts/backups.yaml:
```resources:
  AWS backups:
    type: aws:organizations:Account
    properties:
      email: aws+backups@XXXXXX
      name: AWS backups
      parentId: XXXXXX
      tags:
        Name: AWS backups
        environment: prod
    options:
      protect: true
outputs:
  aws_accounts:
    AWS backups:
      account_id: ${AWS backups.id}```

Pulumi.yaml:
```name: infra
runtime:
  name: yaml
  options:
    compiler: "./spruce.sh"
description: A minimal Pulumi YAML program```