PUT Extensions Scripts
The PUT /Extensions/Scripts method is used to update a script. This method returns HTTP 200 OK on a success with details of the updated script record.
Table 429: PUT Extensions Scripts Input Parameters
Name | In | Description |
---|---|---|
id | Body | Required.
An integer indicating the Keyfactor Command
reference ID for the script.
Use the GET /Extensions/Scripts method (see GET Extensions Scripts) to retrieve a list of all the scripts to determine the ID. |
Contents |
Body |
A JSON-escaped string containing the contents of the script on a single line. Tip: See POST Extensions Scripts for examples of creating and handling this string.
|
Categories | Body |
Required. An array of either integers or case-sensitive strings indicating which category or categories the script applies to. The category of a script cannot be changed if it is in use in any alerts or workflows of that category. Show possible category values. Tip: The list of categories provided will completely replace any previously supported categories for the script. However, you cannot remove a category if the script is configured to be used by that category. You can add additional categories to a script that is already in use by select categories by including the existing categories in the parameter entry and adding any others as desired.
|
Table 430: PUT Extensions Scripts Response Data
Name | Description |
---|---|
id | An integer indicating the Keyfactor Command reference ID for the script. |
Name | A string indicating the user-defined name of the script. The name of a script cannot be changed once posted. |
Contents |
A JSON-escaped string containing the contents of the script on a single line. |
Categories |
An array of either integers or case-sensitive strings indicating which category or categories the script applies to. The category of a script cannot be changed if it is in use in any alerts or workflows of that category. Show possible category values. |