Update an app action
Update one application action
Path parameters
Application id
Action id
Request body
An http/https URL giving the address of the agent receiving the request to initiate the action
A human-readable name. If not specified, a name will be generated from the id
The request method name to be used when making the action request to an agent. Usually POST. Defaults to POST
A textual description of an action. This should describe the effect of the action because it will be presented to the operator who requests running the action before confirming it
A key used to sign requests made to an agent. This is 44 characters (32-bytes, base64-encoded). If not specified, a secret will be generated at creation
A chain of PEM-encoded certificates that can be used to authenticate the agent receiving action requests. If the agent uses a publicly valid X509 certificate that matches the hostname specified in its URL, then this is not needed. This is necessary for self-signed certificates using HTTPS, because the agent is always authenticated. Multiple certificates may be used, for example, when migrating from one certificate to another
Response
The action was successfully updated.
An unchanging identifier for an action that is used when creating a task to run it. All action ids for a subject must be unique
An http/https URL giving the address of the agent receiving the request to initiate the action
A human-readable name. If not specified, a name will be generated from the id
The request method name to be used when making the action request to an agent. Usually POST. Defaults to POST
A textual description of an action. This should describe the effect of the action because it will be presented to the operator who requests running the action before confirming it
A key used to sign requests made to an agent. This is 44 characters (32-bytes, base64-encoded). If not specified, a secret will be generated at creation
A chain of PEM-encoded certificates that can be used to authenticate the agent receiving action requests. If the agent uses a publicly valid X509 certificate that matches the hostname specified in its URL, then this is not needed. This is necessary for self-signed certificates using HTTPS, because the agent is always authenticated. Multiple certificates may be used, for example, when migrating from one certificate to another
Changes
No recorded changes to this endpoint across all 1 revision of this API.