This message was deleted.
# getting-started
s
This message was deleted.
l
If you're in a different directory, then you're viewing different projects, which have different stacks.
a
@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
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
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”