Ammar Bandukwala

As apart of this, we should suggest that persistent resources are named using an ID.

Well, just something stable with the lifecycle of the workspace, so random would be good. If we allow workspace renames I think all existing templates would still work, it's just...

And I suppose we should require that the workspace is offline for a rename to occur to avoid a situation where infrastructure names are misaligned with Coder names.

Do y'all mean that the infrastructure names are static for the lifetime of the workspace? So if I rename my workspace the infrastructure name doesn't change? Beyond the potential to...

> I think semi-deterministic has value for auditing and cleanup. Completely arbitrary/random IDs are more opaque. What are the inputs to a deterministic ID?

A big difference is that the template author chooses the exact naming scheme in v2. So, allowing the workspace is be online during name change also means complicating the UX...

Well it could still work if the persistent resources use ID, for example: ``` resource "docker_volume" "home_volume" { name = "coder-${data.coder_workspace.me.id}-home" } ```

We're talking specifically about the generation of the workspace ID. I don't see any obvious approach to doing that deterministically (barring a timestamp or sequence number which goes against the...

Ok, so you want a deterministic element of the ID, not necessarily the entire ID be deterministic. I can see the value in that. We could generate the workspace ID...

I think that is a separate concern, as the rename feature doesn't impact the orphanage rates. I made https://github.com/coder/coder/issues/3048 to track that.