Ben Potter
Ben Potter
> The problem with dummy keys or passwords is that they are not accessible if they _are_ needed. Yeah, totally agree. Currently, most of our example templates follow that pattern,...
I could also see this being a "root user" only feature.
The only use cases I could think of are automation (in issue description), hence the comment about it being a root feature. Agree we it's something we can wait on...
Some high-priority candidates for July or August: - #2267 - #802 / #2660 - #696 - #1763 - #1624 - #2760 Nice to have - #2659 - #2262 / #2221...
@arivictor would something like this work for your use case of local machines?
My hacky version: https://github.com/bpmct/coder-via-terraform
@deansheather since you did #3176, how would you estimate doing this for `templates` and `workspaces` in the CLI too? unsure if it'd be better to do a generic approach or...
To clarify, just supporting JSON output, not other stuff
This should just be `coder metadata [item-name]`. Secrets isn't a solid use case, as environment variables can be directly mounted and it's not a great pattern to call Coder to...
The issue description has a good template schema, but is missing some UX details, hence the discussion above. Here are some suggestions/mocks. Assigning metadata to a resource: ```hcl # EDIT:...