Ammar Bandukwala

Are you suggesting that on top of the original post's suggestion or instead of? Also environment secrets can already be injected without any new feature, which is why I left...

If you're suggesting that we add a `coder env` command in addition to environment variables, check out how [Vercel approaches the problem](https://vercel.com/docs/concepts/projects/environment-variables). TL;DR they don't have a `vercel env get`...

Vercel provides a `vercel env pull` which produces a `.env` file. That could be used to satisfy rotations and "pull" while still discouraging any deep integration of your software with...

> This should just be `coder workspace metadata`. The workspace commands are at the root, so I assume you mean `coder metadata`? > Secrets isn't a solid use case, as...

I like that mock up. Any open question is whether the metadata should be associated with resources or with the workspace as a whole?

Is `metadata` the best name for this feature? There may be some confusion with `parameters`. `metadata` is a pretty broad term.

@dwahler you're not bikeshedding at all. Feature naming is very important, esp. for marketing which we don't think about enough. I think annotations is pretty good as it doesn't compete...

Thanks @bpmct. What is the expected timeline for an MVP into `main`?

Hey, it looks like the change breaks the hyperlink?

Related #2877