chore: undeprecate the workspace rename flag and clarify potential issues (#21669)

This undeprecates the `allow-workspace-renames` flag. IIUC, the 'danger'
with using this flag is that the workspace name might have been used in
the definition of some other terraform resources within template code,
so a rename could cause problems such as with persistent disks.

for https://github.com/coder/coder/issues/21628

---------

Signed-off-by: Callum Styan <callumstyan@gmail.com>
This commit is contained in:
Callum Styan
2026-01-27 10:53:13 -08:00
committed by GitHub
parent 3ee4f6d0ec
commit d4cd982608
6 changed files with 27 additions and 16 deletions
@@ -57,6 +57,8 @@ To prevent this, use immutable IDs:
- `coder_workspace.me.owner_id`
- `coder_workspace.me.id`
You should also avoid using `coder_workspace.me.name` if your deployment allows workspace renaming via `CODER_ALLOW_WORKSPACE_RENAMES` or `--allow-workspace-renames`.
```tf
data "coder_workspace" "me" {
}