Ben Potter

> Is metadata the best name for this feature? There may be some confusion with parameters. metadata is a pretty broad term. Hmm. How about `annotations`? Seems to be pretty...

> IMO `annotations` is a great term for things like the `quicklinks` example above, but it's not such a good fit for something like an instance ID, where the value...

To my knowledge, we haven't had any user requests for this feature. It does unlock some valuable use cases: - display CPU cores to workspace user - display links to...

After a bit more research, I think `metadata` is still the best name for this feature. As Ammar mentioned, it is a broad term but the feature itself will likely...

@tjcran This is currently in this sprint, the July roadmap, and being worked on. We can consider prioritizing against the August roadmap if necessary

@dwahler that seems reasonable to me. Template admins could add a `count` to the metadata to avoid the try function 🤷🏼 ```diff # main.tf resource "aws-instance" "dev" { count =...

Note: I'll write the docs for this once the frontend comes in and close the issue once that is complete.

Ah - good catch @docfactory37! We haven't added the "admin user setup" screen to the web UI yet. > i have tried to console into the docker container and run...

@docfactory37 the Docker version is ready, you just need to use the CLI on your client to set up the user. Ah I see. That's our docs for Coder Classic....

@docfactory37 You'll need to download the Coder CLI from https://coder.com/docs/coder-oss/latest/install#manual I have a feeling you were using our V1 (Classic) CLI. We'll add a note to clarify this.