Configuring Project Template fails despite inclusion of required attributes for roles

[carl-reverb]

I'm trying to configure a project template for my (enterprise) organization, but I get a 422 error complaining that the role name and slug are not present. However, they are present in my resource definition.

Could not create project template: CallCreateProjectTemplate Unsuccessful response [POST https://app.infisical.com/api/v1/project-templates] [status-code=422] [request-id=req-dPnIuGjmFLmy5d] [message="{"reqId":"req-dPnIuGjmFLmy5d","statusCode":422,"message":"{
  "reqId": "req-dPnIuGjmFLmy5d",
  "statusCode": 422,
  "message": [
    {
      "code": "too_small",
      "minimum": 1,
      "type": "string",
      "inclusive": true,
      "exact": false,
      "message": "String must contain at least 1 character(s)",
      "path": [
        "roles",
        0,
        "name"
      ]
    },
    {
      "code": "too_small",
      "minimum": 1,
      "type": "string",
      "inclusive": true,
      "exact": false,
      "message": "Slug field must be at least 1 lowercase character",
      "path": [
        "roles",
        0,
        "slug"
      ]
    },
    {
      "code": "invalid_type",
      "expected": "array",
      "received": "null",
      "path": [
        "roles",
        0,
        "permissions"
      ],
      "message": "Expected array, received null"
    }
  ],
  "error": "ValidationFailure"
}"]

My resource:

resource "infisical_project_template" "reverb-apps" {
  name        = "reverb-apps"
  description = "Template for Reverb applications to standardize roles."
  type        = "secret-manager"

  roles = [{
    name        = "Admin"
    description = "Admin role with full permissions."
    slug        = "admin"

    permissions = local.template-permissions.admin
    }, {
    name        = "Developer"
    description = "Developer role with limited permissions."
    slug        = "dev"

    permissions = local.template-permissions.developer
  }]
}

As an example of the developer permissions (for brevity):

locals {
  template-permissions = {
    developer = [
      {
        subject = "secrets",
        action  = ["describeSecret", "read", "readValue", "create", "edit", "delete"]
      },
      {
        subject = "secret-rollback",
        action  = ["read", "create"]
      },
    ]
  }
}

Provider version = "0.15.46"

[carl-reverb]

Actually, I think that the backend simply has bad feedback when a template's roles collide with the forced builtin roles of admin, developer, etc.

This resource, probably other things, could benefit significantly from provider validations.