https://pulumi.com
Join Slack
This message was deleted.
# getting-started
s
This message was deleted.
s
This isn’t currently possible.
s
when I see this I think of parent/child relationships between stacks
Copy code
View in Browser (Ctrl+O): <https://app.pulumi.com/me/dev-eks/dev-charts-system/updates/3>

     Type                 Name                       Status      Info
     pulumi:pulumi:Stack  dev-eks-dev-charts-system  running.    read pulumi:pulumi:StackReference openphone/dev-eks/dev-eks
s
The FQSN (fully qualified stack name) is 
organization/project/stack
, and AFAIK there’s no way to modify or extend that to allow a stack to be parent to another stack. I’m also not sure of the use case---what was your thought process around this, if I may ask?
📝 1
s
just a way of conceptualizing the relationship between stacks vertically.
it could be totally totally ill conceived I'm new here
s
Sometimes the best questions are asked by those who are new to something. 😄
s
ty! I'm proud to always be the dumbest person in the room. 🤠
s
There is no such thing as a dumb question, and therefore you are not the dumbest person in the room. 🙂
s
This is what I suspected should have existed and be more front and center in pulumi project design https://github.com/pulumi/pulumi-auto-deploy
you guys call it dependent stacks https://github.com/pulumi/pulumi-auto-deploy
s
Yes---stacks where there is a dependency (via a StackReference) to another stack, such that changes in one stack might necessitate updates in one of the dependent stacks.
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by