https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
f
I reserve the right to "not get it" too 🙂
b
I believe there is an open issue about this 😄
I am trying to find it...
f
Cool, I'll give it a 👍 . (Couldn't find it either)
w
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
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
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
Thanks for the validation @white-balloon-205; will do that.
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by