@sharkymark I'm VERY sorry for that. I already found the bug and fixed it. Waiting for the PR to be reviewed and tests to release a PATCH version.

I'm not convinced that #7221 fixes it, as the backend should pull parameters from the previous build. Actually, I'm having trouble reproducing it.

@sharkymark how Marcin tried to reproduce it:

• Create a template with params
• Create a workspace
• Push new template version with params.
• Update workspace. I can see the popup for the new parameter.
• Workspace is updated and contains old parameter values.

Initial parameters

data "coder_parameter" "random_string_required" {
  name        = "Required random string"
  icon        = "/icon/aws.png"
  description = "This string is required"
  mutable     = true
}

Added parameters:

data "coder_parameter" "random_string_required_new" {
  name        = "Second required random string"
  icon        = "/icon/aws.png"
  description = "This string is required"
  mutable     = true
}

We are unable to reproduce it, and it seems to work correctly, so I'm lowering the severity. I think that we need the exact template and more info about users/permissions to start digging into this.