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.

Pulumi Community

is it possible to reference a remote pulumi stack (for example, in a different s3 bucket)?

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.

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

&gt; even different paths inside the same s3 bucket are currently effectively the different backends

I would not have expected that to be the case.

&gt; 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?

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 &lt;org-name&gt;/&lt;stack-name&gt; (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

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.

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