If you're in a different directory, then you're viewing different projects, which have different stacks.
a
acoustic-lawyer-27551
04/21/2023, 6:11 PM
@little-cartoon-10569 thanks for your response. I am using .envrc file to authenticate into an aws s3 bucket which hosts the state so as long as I’m under that .envrc file, I will be able to see all stacks created under that state
l
little-cartoon-10569
04/22/2023, 1:24 AM
Yes, but the "pointer" into that state is defined by the Pulumi.yaml file in the current directory (or as specified by command-line parameters). If you change directory, you're looking at a different project, which means different stacks.
a
acoustic-lawyer-27551
04/24/2023, 4:57 PM
Ok that makes sense. But for the issue I’m having, how could there be a “organization/<pulumi name>/” appended to the beginning of a stack name when I switch to a different directory? For ex. I’m in the apps/security folder and can see two stacks, “pulumi-security” and “organization/infra/pulumi-infra”. When I move back a directory and into the infra directory, for ex, I see the same two stacks listed with different names: “pulumi-infra” and “organization/security/pulumi-security”
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.