sparse-intern-71089
03/28/2019, 10:20 PMbusy-pizza-73563
03/28/2019, 10:31 PMenvironment-name
only, in pulumi
output I can see
Type Name
pulumi:pulumi:Stack project-name-environment-name
colossal-beach-47527
03/28/2019, 10:32 PMproduction
. You can also have multiple stacks within the same project, e.g. payment-system
.
As far as best practices, yes, we would encourage you to name your stacks something related to the environment. So your production stack would be named production
, and so on.
Before we changed the stack identity model (which was a month or so ago IIRC), that meant you needed to name things project-name/env-name
. But now you should be able to just name your stacks env-name
. (And it will be OK, since we use the project name as part of its identity.)
/cc @bitter-oil-46081 who can cover this in better detail.bitter-oil-46081
03/28/2019, 10:33 PMbusy-pizza-73563
03/28/2019, 10:33 PMbitter-oil-46081
03/28/2019, 10:34 PMbusy-pizza-73563
03/28/2019, 10:35 PMRight now due to a bug there are not namespace by project when using the filesystem backend.Oh, ok, that was my best guess, too.
bitter-oil-46081
03/28/2019, 10:35 PMbusy-pizza-73563
03/28/2019, 10:36 PMbusy-pizza-73563
03/28/2019, 10:37 PMbusy-pizza-73563
03/28/2019, 10:38 PMdev
out of aws-infra-dev
)busy-pizza-73563
03/28/2019, 10:41 PMpulumi.StackReference()
expect only that <project-name>-<stack-name>
name? Or should it be <project-name>/<project-name>-<stack-name>
?busy-pizza-73563
03/28/2019, 10:45 PMcolossal-beach-47527
03/28/2019, 10:49 PMpulumi.StackReference()
, both would probably work. If I recall correctly, the API was written in such a way that we would automatically support newer and older stack identities seamlessly. But we will report an error if it is ambiguous. (e.g. if two stacks have the same name, and only differ via project name.)
But when using the local backend, I cannot say for sure.busy-pizza-73563
03/28/2019, 10:56 PMbusy-pizza-73563
03/31/2019, 7:31 PMRight now due to a bug there are not namespace by project when using the filesystem backend.@bitter-oil-46081 Do you know if there's an issue I can follow?