Policy resource: priority option in script declaration not working

[ecanault]

Description

When you add a script in a policy, you may want to change its priority (BEFORE or AFTER).

Expected behavior

Setting the priority of a script in a policy should be reflected in Jamf Pro.

Actual behavior

Even if the priority is correctly defined in the plan, the result in Jamf Pro is not correct:

+ script {
          + id         = "330"
          + name       = (known after apply)
          + parameter4 = "googlechrome"
          + priority   = "AFTER"
}

Possible explanation

?

Possible fix

?