Based on the identifier format and status you've shared, this appears to be a work item or ticket related to fixing load options when creating condition sets in Permit.io. Looking at the condition set creation functionality, here's how condition sets are created according to the documentation: For ​*User Sets*​, you define conditions that match users (1) :

{
  "key": "us_based_employees",
  "name": "US based employees",
  "type": "userset",
  "conditions": {
    "allOf": [
      {
        "user.role": {
          "equals": "employee"
        }
      },
      {
        "user.location": {
          "in": [
            "US"
          ]
        }
      }
    ]
  }
}

For ​*Resource Sets*​, you define conditions that match resources :

{
  "key": "private_repositories",
  "name": "Private Repositories",
  "type": "resourceset",
  "conditions": {
    "allOf": [
      {
        "resource.type": {
          "equals": "repository"
        }
      },
      {
        "resource.access": {

The Node.js SDK provides a

create

method for condition sets (2) :

create(conditionSetData: ConditionSetCreate) : Promise<ConditionSetRead>;

And the Ruby SDK shows the API endpoint structure (3) :

def create_condition_set(proj_id, env_id, condition_set_create, opts = {})
  data, _status_code, _headers = create_condition_set_with_http_info(proj_id, env_id, condition_set_create, opts)
  data
end

The creation requires specifying the project ID and environment ID along with the condition set data .

Hmm.. Seems there was an issue processing this question. Please try again or tag a team member.