Parametermutablity is determined by the current state. So a previouslyimmutable parameter can becomemutable.

Terraform:

data"coder_parameter""isimmutable" {name="isimmutable"type="bool"mutable=truedefault="true"}data"coder_parameter""immutable" {name="immutable"type="string"mutable=data.coder_parameter.isimmutable.value=="false"default="Hello World"}

Trivial Case:

1. Workspace built withisimmutable = true &immutable = "bar"
2. Workspace updatesimmutable = foo
   1. Breaks, because you cannot update an immutable value

Immutability source from the past

1. Workspace built withisimmutable = true &immutable = "bar"
2. Workspace updatesimmutable = foo &isimmutable = false
   1. This works because at validation time,mutable = true

Why ignore the previous parameter state?

Ignoring previous state is vastly simplier and more intuitive. If the previous parametermutability affected the current build, then questions such as, "What if the last build failed? Do we take the last successful build?", etc.