is there anyway to split Pulumi.<stack>.yaml to multiple files or import another file? my config is too big, so it very hard for user to edit a big file My only idea is store config in python file (but format is more verbose than YAML)

@modern-art-40204 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/

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 😃 )

@modern-art-40204 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}