│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to xray_license_policy.license_policy, provider "provider[\"registry.terraform.io/jfrog/xray\"]" produced an unexpected new value: .rule: planned set element
│ cty.ObjectVal(map[string]cty.Value{"actions":cty.SetVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"block_download":cty.SetVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"active":cty.False,
│ "unscanned":cty.False})}), "block_release_bundle_distribution":cty.False, "block_release_bundle_promotion":cty.False, "build_failure_grace_period_in_days":cty.NumberIntVal(0),
│ "create_ticket_enabled":cty.False, "custom_severity":cty.StringVal("medium"), "fail_build":cty.True, "mails":cty.NullVal(cty.Set(cty.String)), "notify_deployer":cty.False,
│ "notify_watch_recipients":cty.False, "webhooks":cty.NullVal(cty.Set(cty.String))})}), "criteria":cty.SetVal([]cty.Value{cty.ObjectVal(map[string]cty.Value{"allow_unknown":cty.False,
│ "allowed_licenses":cty.NullVal(cty.Set(cty.String)), "banned_licenses":cty.NullVal(cty.Set(cty.String)), "multi_license_permissive":cty.True})}), "name":cty.StringVal("alp-license-rule"),
│ "priority":cty.NumberIntVal(1)}) does not correlate with any element in actual.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Is your feature request related to a problem? Please describe.
"medium" was used instead of "Medium" for custom severity in license policy. Error returned did not point out the problem.
Describe the solution you'd like
Friendlier errors when validation errors are encountered.
Something like. Validation Error: "medium" is not a valid custom severity. Valid values are "Low", "Medium" or "High"
I thought the REST API would return the validation errors.
Maybe we are swallowing and not displaying them in the provider?
** Example terraform
** Example error
Is your feature request related to a problem? Please describe. "medium" was used instead of "Medium" for custom severity in license policy. Error returned did not point out the problem.
Describe the solution you'd like Friendlier errors when validation errors are encountered.
Something like.
Validation Error: "medium" is not a valid custom severity. Valid values are "Low", "Medium" or "High"
I thought the REST API would return the validation errors.
Maybe we are swallowing and not displaying them in the provider?