This message was deleted.
# general
s
This message was deleted.
v
We use stackReferences here at my place to leverage the stack outputs. its the neatest way we have found, its also handy that its programatic so changes will be detected automatically when you run pulumi next. One challenge is obviously if a dependent service needs updating, is triggering a pulumi run of that service. Something in my personal backlog is to investigate using the pulumi stack graph command to leverage automated pulumi ups from dependent stacks
pulumi config is completely different and should be used for project specific configurations such as environment, region, etc etc
m
Is StackReferences specific to AWS? We're using GCP/Python. Currently, we retrieve stack information using:
Copy code
stack = automation.select_stack(
        stack_name=get_stack(),
        project_name=project_name,
        program=lambda: None,
    )
Which returns an object that includes things like the outputs.
In respect of updating dependent projects, that might depend a bit on the deployment setup. To keep things a bit manageable (for now), we try to keep our deployment pipeline monolithic. We now have one single pipeline that executes the pulumi updates for each project, one after another. That might change in the future of course. We're in the midst of a cloud migration from on-prem Docker Swarm to K8s/GKE/GCP.
b
@victorious-church-57397 https://github.com/gitfool/Pulumi.Dungeon does something like that. Stack orchestration basically.
v
i dont think we are talking about the same thing @bored-activity-40468 - we have multiple stacks in the aws accounts and need outputs from each of them, they are stored in separate repos. This looks like wrapping all the pulumi resources you need in a class in one repo
and doing multiple environments, which we already do using pulumi stacks 🙂 thanks for the link though, will check it out further
b
That's true, I was more talking about how with automation-api that stackref or stack dependency enforcement can be built in. Even though that example has multiple stacks in the same repo, since we get to use a real programming language, the dependency ref could just as easily be a link to another repo.