https://pulumi.com logo
Powered by
f

fresh-summer-65887

07/08/2019, 11:22 AM
Why do fully qualified stack names not include the project name? On the website it's 
{org-name}/{project-name}/{stack-name}
in the UI and URLs. On the CLI it's 
{org-name}/{stack-name}
. This gets confusing when you have two projects in the same org with the same 
{stack-name}
.
I reserve the right to "not get it" too 🙂
b

broad-dog-22463

07/08/2019, 11:23 AM
I believe there is an open issue about this 😄
I am trying to find it...
f

fresh-summer-65887

07/08/2019, 11:25 AM
Cool, I'll give it a 👍 . (Couldn't find it either)
w

white-balloon-205

07/08/2019, 1:19 PM
Where specifically are you seeing it be 
org-name/stack-name
? There is an issue that the local backend still uses 
org-name/stack-name
, but everything in the CLI that works with the pulumi.com backend should be including project name. When you are in the context of a project (in a folder with a Pulumi.yaml), many CLI verbs will allow specifying things without project-name being explicit.
See https://github.com/pulumi/pulumi/issues/2522 for the local backend issue here.
f

fresh-summer-65887

07/08/2019, 2:01 PM
Here is an example:
(in a folder with a Pulumi.yaml), many CLI verbs will allow specifying things without project-name being explicit.
Is the org name required then too?
At this time, I'm confident to say that I'd prefer to see the explicit name here 
LykkeCorp/sample-react-app/sandbox
For whatever reason, it make me a bit uncomfortable "Am I pointing at the right sandbox stack"
w

white-balloon-205

07/08/2019, 4:32 PM
Would you mind opening an issue at https://github.com/pulumi/pulumi/issues/new to track the suggestion to be more explicit here - and the reasons you want that? I do agree that these should most likely be explicit even when in a project context.
f

fresh-summer-65887

07/09/2019, 7:25 AM
Thanks for the validation @white-balloon-205; will do that.
Powered by