https://pulumi.com logo
#general
Title
# general
b

bored-river-53178

07/03/2019, 10:25 PM
is it possible to reference a remote pulumi stack (for example, in a different s3 bucket)?
w

white-balloon-205

07/03/2019, 10:43 PM
It is only possible to reference other stacks that share the same "backend", and today, each S3 bucket is it's own "backend". So although you can reference state in other stacks managed in the same S3 bucket backend, you cannot reference stacks in other backends entirely.
b

bored-river-53178

07/03/2019, 10:45 PM
and even different paths inside the same s3 bucket are currently effectively the different backends, is that right?
I am trying to solve the same issue as described here https://github.com/pulumi/pulumi/issues/2814 but the last comment does not reflect the current state of things
I can't use stack references with '/' in their names
w

white-balloon-205

07/03/2019, 10:48 PM
even different paths inside the same s3 bucket are currently effectively the different backends
I would not have expected that to be the case.
as described here https://github.com/pulumi/pulumi/issues/2814 but the last comment does not reflect the current state of things
In what sense is that issue not correct?
b

bored-river-53178

07/03/2019, 10:51 PM
how can I create a stack with '/' in its name using s3 backend?
Please enter your desired stack name. To create a stack in an organization, use the format <org-name>/<stack-name> (e.g.
acmecorp/dev
): test/test error: could not create stack: validating stack properties: invalid stack name: a stack name may only contain alphanumeric, hyphens, underscores, or periods
w

white-balloon-205

07/03/2019, 10:51 PM
Ahh - got it. Yes - https://github.com/pulumi/pulumi/issues/2522 is the key issue blocking this currently.
The comments in https://github.com/pulumi/pulumi/issues/2814 were relative to assuming that https://github.com/pulumi/pulumi/issues/2522 will be fixed, and what to do once it is fixed.
b

bored-river-53178

07/03/2019, 10:52 PM
this issue is quite old. is there some kind of workaround?
tried
pulumi stack rename "core/global"
and that worked, but there is no way to access the renamed stack afterwards,
pulumi stack ls
is empty