The configuration of projects stack names are rather frustra Pulumi Community #general

Join Slack

The configuration of projects / stack names are ra...

# general

quiet-wolf-18467

10/08/2018, 5:24 PM

The configuration of projects / stack names are rather frustrating

quiet-wolf-18467

10/08/2018, 5:25 PM

Projects seem to be a way of grouping stacks, which is fine

quiet-wolf-18467

10/08/2018, 5:25 PM

However, as stack names need to be unique, you end up being rather verbose

quiet-wolf-18467

10/08/2018, 5:25 PM

Example: Project:

rawkodes-modern-life

quiet-wolf-18467

10/08/2018, 5:26 PM

Stack can't be

production

, due to the unique constraints, so it ends up

rawkodes-modern-life-production

quiet-wolf-18467

10/08/2018, 5:26 PM

It just feels really clunky

quiet-wolf-18467

10/08/2018, 5:27 PM

And the required

Pulumi.stsckname.yaml

is annoying too

quiet-wolf-18467

10/08/2018, 5:31 PM

Copy code

Type                                 Name                                                  Status      Info
 -   pulumi:pulumi:Stack                  rawkodes-modern-life-rawkodes-modern-life-production  deleted

quiet-wolf-18467

10/08/2018, 5:31 PM

My OCD isn't coping 😂

quiet-wolf-18467

10/08/2018, 5:39 PM

The more I'm playing with this, it seems to be a wrapper around Terraform's workspaces?

quiet-wolf-18467

10/08/2018, 5:46 PM

Ah, now I see the GCP definitions are generated from Terraform's provider. Is this how most of Pulumi works?

white-balloon-205

10/08/2018, 6:15 PM

The project/stack structure is unrelated to Terraform Workspaces (though I suppose most solutions to providing separate environments and deployments of a single project have some fundamental similarities :-)). You are right that because the identity of a stack is

<user/org>/<stackname>

, the stack name generally has to be a little more verbose to remain unique within an organization. We used to have identity tracked as

<user/org>/<project>/<stackname>

, which allowed the stack name to be something more like

production

, as it was scoped to a project. It sounds like this would align closer with how you wanted to think about things. We're continuing to look at refactoring things in this direction again - but for now you can generally map into this mental model just be making all stacknames look like

<project>-<stack>

(which appears to be what you are doing). The fact that that

pulumi:pulumi:Stack

row duplicates this information is just a bug - see https://github.com/pulumi/pulumi/issues/1417.

white-balloon-205

10/08/2018, 6:17 PM

I see the GCP definitions are generated from Terraform's provider. Is this how most of Pulumi works?

The AWS, Azure and GCP resource providers build on top of the

terraform-resources-providers

for these platforms, but use the

pulumi

CLI and engine for driving deployments.

quiet-wolf-18467

10/08/2018, 6:25 PM

Thanks for the info

quiet-wolf-18467

10/08/2018, 7:22 PM

<user/org>/<project>/<stackname>

makes a lot more sense to me 🙂

tall-librarian-49374

10/08/2018, 7:44 PM

I also had similar concerns, trying to grasp how stacks should be used and how to give them shorter names. Stack local to project would make sense to me. I don't have large infra though, so my only use case for multiple stacks were deployments on different cloud accounts.

cool-helicopter-70130

10/09/2018, 5:25 AM

I also expected

<user/org>/<project>/<stackname>

, and and spent 10 mins creating and destroying stacks until I stopped being confused.

glamorous-printer-66548

10/09/2018, 6:59 AM

@quiet-wolf-18467 @tall-librarian-49374 @cool-helicopter-70130 I had the exact same observation about stack / project names a couple of days ago (https://pulumi-community.slack.com/archives/C84L4E3N1/p1537128934000100). Now just just created a github issue out of it. Please add your vote to the gh issue 🙂 https://github.com/pulumi/pulumi/issues/2039

👍 2

Open in Slack

Previous Next