Related to a prior question how does one tell a `pulumi Stac

Question

Related to a prior question how does one tell a `pulumi StackReference` to look at a stack in another S3 bucket by stack name i e I m in `bar deploy` I need to access `foo deploy` but I need to specifically get outputs from the `dev` stack use case there might be multiple `bar deploy` stacks using `foo deploy` `dev` as their backend How can I express this

handsome-actor-1155 · Answer

`const stackRef = new pulumi StackReference accountname foo deploy dev `

boundless-monkey-50243 · Answer

How s that work with S3 buckets though

boundless-monkey-50243 · Answer

I saw you were the other person asking around about this the other day ha

boundless-monkey-50243 · Answer

Like say my target is `` how do I get the `dev` stack from it `` doesn t work

boundless-monkey-50243 · Answer

I get `NotFoundKey` errors so it s looking for something just can t find it Next stop is CloudTrail I guess anguished

handsome-actor-1155 · Answer

Not sure about s3 tbh Sorry

boundless-monkey-50243 · Answer

doh Thanks though I was told by < white balloon 205> it was doable sometime last week just have to find the magic words

white-balloon-205 · Answer

I think I would have expected that to work as written assuming a stack by that name exists in the same S3 backend If you verify that stack does exist but isn t being looked up here could you open an issue so we can investigate

boundless-monkey-50243 · Answer

Wait I think we re using different definitions of the same backend

boundless-monkey-50243 · Answer

I take it to mean the same S3 account accessed with the same S3 credentials No

boundless-monkey-50243 · Answer

If it s literally the same `pulumi login` d stack then that s going to be a real problem and I m gonna look like an idiot confused

white-balloon-205 · Answer

Could you describe the full scenario you are looking to enable I m not sure I follow why you would want need to have different `pulumi login`s for the same S3 bucket In general at least currently the backend you are logged into is the context for discovering and referencing all the stacks that you have available

boundless-monkey-50243 · Answer

I am looking to allow somebody in for example the `app deploy` workspace to be able to acquire data out of say the `network base` workspace keyed to a particular stack

boundless-monkey-50243 · Answer

Having read write to `app deploy` does not imply write access to `network base` regardless of environment Pulumi stack being worked on

boundless-monkey-50243 · Answer

I don t really want to use prefixes inside of a single ` pulumi` directory because it 1 makes for what I think are less comprehensible IAM policies and 2 means then that my developers have to remember and they will not remember to do stuff like `pulumi stack some app dev` in their working directories rather than `pulumi stack dev` If it helps the analogy I m looking for is to separate `terraform tfstate` files

boundless-monkey-50243 · Answer

I want my application to be able to go I m a `dev` stack I m going to look for the `dev` stack in `network base` and find out my VPC CIDR block

boundless-monkey-50243 · Answer

I could be totally misunderstanding something clever to be clear If so maybe it s useful as something to underline in the docs wink

shy-receptionist-99213 · Answer

we re also lookign for the same solution For example infrastructure team uses `pulumi login ` and services have `pulumi login ` How do we reference `infra` from `service` ones

boundless-monkey-50243 · Answer

That s a good point and it hits on at having a single `pulumi login` at a system level too This feels like it should be per directory

boundless-monkey-50243 · Answer

< white balloon 205> As an example of why this is gross if everything s in a single stack repo I have to tell my developers to do stuff like `pulumi stack switch dev deploy data api v2` and to be aware of eye popping files like `Pulumi dev deploy data api v2 yaml` Admittedly this might be a little vain but that s just really unpleasant to be throwing in a repo when the file itself lives in `data api v2 deploy` because we also have a `data api v2 build` Pulumi I keep wanting to call them stacks workspace that contains our CodeBuild CodePipeline etc definitions

boundless-monkey-50243 · Answer

It just really doesn t feel like the single namespace model holds up at moderate scale

shy-receptionist-99213 · Answer

Looks like `name` from pulumi yaml is not used for file location similar to pulumi backed where it s used for namespacing

shy-receptionist-99213 · Answer

Semi related issue <https github com pulumi pulumi issues 2800>

boundless-monkey-50243 · Answer

I was wondering about that yeah I wonder if that s not the easiest solution Though it ll break existing s3 users

shy-receptionist-99213 · Answer

Some migration can be provided as terraform does this

boundless-monkey-50243 · Answer

< shy receptionist 99213>