Potential UI bug with require_predefined_choice

[mfickley]

Hi!

When utilizing the require_predefined_choice in my options, it doesn't seem to apply in the Rundeck UI as expected.

Given this code:

  option {
    label                     = "ServerName"
    name                      = "ServerName"
    required                  = "true"
    value_choices             = ["Server1", "Server2", "Server3"]
    sort_values               = "true"
    require_predefined_choice = "true"
  }

After applying this, the Rundeck UI displays a freeform textbox for the option as well as a validated drop down list. I only want the predefined dropdown list.

If I go into the option settings in the UI, "Restrictions ' are set to "None" instead of "Enforced from Allowed Values" as I'd expect when setting require_predefined_choice = "true". I've manually checked the box to "Enforced from Allowed Values" then run terraform plan again to see if I missed a setting, but the plan comes back as matching.

Rundeck Version v5.19.0-20260203
terraform-provider-rundeck v1.1.2

[mfickley]

I just realized that if you change other attributes of the job then redeploy, it re-adds those free-text fields.

[fdevans]

Thanks for reporting this! We found the issue - the provider was sending the wrong API field name for option enforcement.

According to the Rundeck Job-JSON documentation, the field should be enforced, but we were sending enforcedValues instead. This caused Rundeck to ignore the restriction setting.

We've fixed this in the upcoming 1.2.0 release. After the update, setting require_predefined_choice = true will properly enforce the dropdown restriction in the UI as expected.