Hi @mattlqx do you have any issues while setting it. O think it should work of you also set the type = "number".
Or you need string values you can later use the tostring() function where you use this parameter.

@mtojek don't we support options for the type = "number"? I see that the type for both name and value is required to be string in the provider.

The problem seems to be actually that options don't support validation.

2024-01-12 20:47:07.520Z Error: Conflicting configuration arguments
2024-01-12 20:47:07.520Z on params.tf line 77, in data "coder_parameter" "home_volume_size":
2024-01-12 20:47:07.520Z   77: data "coder_parameter" "home_volume_size" {
2024-01-12 20:47:07.520Z 
2024-01-12 20:47:07.520Z "validation": conflicts with option

That's with the following attributes:

  default     = "300"
  mutable     = true
  type        = "number"

  option {
    name  = "300 GB (Default)"
    value = "300"
  }

  option {
    name  = "600 GB"
    value = "600"
  }

  option {
    name  = "1 TB"
    value = "1000"
  }

  validation {
    monotonic = "increasing"
  }

We should definitely support monotonic type validation for options with type number.

cc: @coder/pms @mtojek

I second what Matt said about the problem.

Coder enables validation for number fields, but since there are options provided, it assumes that it does not need advanced validation. Hence there is a type conflict. It is aligned with the initial design of Coder parameters which assumed that parameter options are only strings.

This issue is kind of a whack-a-mole challenge. Fix all places, hopefully only in Coder, until it works correctly.