synced/coder
1
0
Fork 0
mirror of https://github.com/coder/coder.git synced 2025-07-12 00:14:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: reduce ignore_changes suggestion scope (#17947)

Browse Source 
We probably shouldn't be suggesting `ignore_changes = all`. Only the
attributes which cause drift in prebuilds should be ignored; everything
else can behave as normal.

---------

Signed-off-by: Danny Kopping <dannykopping@gmail.com>
Co-authored-by: Edward Angert <EdwardAngert@users.noreply.github.com>
This commit is contained in:
Danny Kopping
2025-05-20 22:16:23 +02:00
committed by GitHub
parent 1f54c36375
commit d2d21898f2
1 changed files with 3 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/admin/templates/extending-templates/prebuilt-workspaces.md
View File

@ -142,7 +142,7 @@ To prevent this, add a `lifecycle` block with `ignore_changes`:
```hcl
resource "docker_container" "workspace" {
lifecycle {
ignore_changes = all
ignore_changes = [env, image] # include all fields which caused drift
}
count = data.coder_workspace.me.start_count
@ -151,19 +151,8 @@ resource "docker_container" "workspace" {
}
```
For more targeted control, specify which attributes to ignore:
```hcl
resource "docker_container" "workspace" {
lifecycle {
ignore_changes = [name]
}
count = data.coder_workspace.me.start_count
name = "coder-${data.coder_workspace_owner.me.name}-${lower(data.coder_workspace.me.name)}"
...
}
```
Limit the scope of `ignore_changes` to include only the fields specified in the notification.
If you include too many fields, Terraform might ignore changes that wouldn't otherwise cause drift.
Learn more about `ignore_changes` in the [Terraform documentation](https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle#ignore_changes).