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.

Pulumi Community

Aside from running `pulumi stack ls` (or making an equivalent API call), is there _any_ way to determine the active stack for a Pulumi project? I'm not seeing anything in the stack-specific YAML files that would denote active or not.

There is but I wouldn't recommend using it. Every project directory makes a file in ~/.pulumi/workspaces which looks like "&lt;project_name&gt;-&lt;hash_of_path&gt;-workspace.json" and that records the active stack.

Relevant code:
```func (pw *projectWorkspace) settingsPath() string {
	uniqueFileName := string(pw.name) + "-" + sha1HexString(pw.project) + "-" + WorkspaceFile
	path, err := GetPulumiPath(WorkspaceDir, uniqueFileName)
	contract.AssertNoErrorf(err, "could not get workspace path")
	return path
}

// sha1HexString returns a hex string of the sha1 hash of value.
func sha1HexString(value string) string {
	// nolint: gosec
	h := sha1.New()
	_, err := h.Write([]byte(value))
	contract.AssertNoError(err)
	return hex.EncodeToString(h.Sum(nil))
}```
So you _could_ get the sha1 hex string of the Pulumi.yaml file then look it up there, but
A) That's horrible just use `pulumi ls`
B) This is _not a supported_ interface and we'll probably move those files to somewhere more sensible at some point

But that's the state of things now if the risk tradeoff is worth it to you.

Hmm...OK, thanks. I was asking because I was trying to incorporate support for displaying the active Pulumi stack in the prompt using `powerline-go` (<https://github.com/justjanne/powerline-go>). Doing something local would generally result in lower latency (useful for a prompt) than having to call out to the Pulumi service.

Oh if your in the project directory `pulumi stack --show-name`

I'll give that a look. Does that make a call out to the service in order to return the value?

This is what Starship (another popular PS1 written in Rust) does <https://github.com/starship/starship/blob/master/src/modules/pulumi.rs#L116>

N.B. Aaron works at Pulumi :slightly_smiling_face:
And `pulumi stack --show-name` was recently changed to be _much_ faster (hopefully fast enough for a PS1 prompt) I'll nudge Aaron to see about changing starship to try using it as well.

Oh it looks like I linked his fork instead of the upstream

Yes him and Ian have both made changes to that module (<https://github.com/starship/starship/pull/3055> + <https://github.com/starship/starship/pull/3428>)

I don’t know Rust, but it looks like it’s parsing the JSON files in `~/.pulumi/workspaces`. I have a fork of `powerline-go` working using `pulumi stack --show-name`, but there is a noticeable delay in the prompt. I’ll have to try parsing the JSON files and see if that works better.