https://pulumi.com logo
Title
w

white-balloon-205

04/04/2023, 4:15 AM
A common question (and one of the most requested features in pulumi/pulumi!) has been the inconsistent support for Projects across Pulumi Service and Self-Managed Backends. With today's CLI release (3.61.0), we've aligned these into the same model, with support for Projects in the Self-Managed Backends (file, S3, etc.). Additional details in this post from @incalculable-parrot-23117 and @microscopic-pilot-97530. 😛ulumipus-dancing-music: https://www.pulumi.com/blog/project-scoped-stacks-in-self-managed-backend/
e

enough-painter-7423

04/04/2023, 10:37 AM
This is a wonderful update! Is it possible to add some info on how this change might impact stack references? Maybe it works just the same as https://www.pulumi.com/blog/project-scoped-stacks-in-self-managed-backend/#referencing-stacks-in-the-cli but it'd be ideal to have some official clarification before I do format upgrade
i

incalculable-parrot-23117

04/04/2023, 4:35 PM
@enough-painter-7423 Yes it does! Stack references now work the same way as the Pulumi service:
$org/$proj/$stack
to reference stacks. Before this update—before project-scoped stacks, stack references in the self-managed backend could only use
$stack
(which had to be globally unique within that backend).