更新处理器预设

OpenAPI 契约

方法

PUT

路径

/api/v1/processors/{id}

认证

jwtBearer (bearer) OR automationKey (bearer)

响应状态

200 400 401 403 404 429 500

请求与响应 Schema

JSON

{
  "requestBody": {
    "application/json": {
      "$ref": "#/components/schemas/UpdateProcessorRequest"
    }
  },
  "responses": {
    "200": {
      "description": "Processor preset updated",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/ProcessorPresetResponse"
        }
      }
    },
    "400": {
      "description": "Invalid request",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/RequestError"
        }
      }
    },
    "401": {
      "description": "Authentication required or invalid",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/SecurityError"
        }
      }
    },
    "403": {
      "description": "Authenticated but not permitted",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/SecurityError"
        }
      }
    },
    "404": {
      "description": "Requested processor preset was not found",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/ApiError"
        }
      }
    },
    "429": {
      "description": "Rate limit exceeded",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/SecurityError"
        }
      }
    },
    "500": {
      "description": "Unexpected server error",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/ApiError"
        }
      }
    }
  }
}

PUT /api/v1/processors/{id} 接受 JWT 或带 processor:write 的 nfy_ 密钥，并且仅限所有者。其实现是部分更新：省略的字段保持不变，非 null 的 steps 列表在通过特性验证后替换所有保存的步骤。步骤 args 仍只是存储的元数据，列表位置也不控制构建执行；只会解析特性 ID。native-unsafe 与 native-llvm-direct-call 是相互独立的 LLVM_CONFIG 编译器特性，可同时保存。该组合已在现有 Java 8 工作负载中验证，但尚未穷尽所有 JVM、平台或输入；发布前请用有代表性的工作负载测试精确配置。

http

PUT /api/v1/processors/{id}
Authorization: Bearer <access token>
Content-Type: application/json

{"steps":[{"feature":"native-llvm-direct-call","args":""}]}