Change a plugin's properties, such as name, description, code, group membership, etc.
The default group a plugin belongs to.
Description of the plugin.
Is plugin enabled.
Name of the plugin, which must be unique within an account.
Type of a plugin.
A detached OpenPGP signature over the plugin source code.
The signature packet must be armored. If the account has a plugin code signing policy, the signature is required in the following cases:
- when creating a new plugin
- when updating the plugin code
Language of plugin code.
Set of all the groups that plugin is part of.
Set of all the groups that plugin is part of.
Set of all the groups that plugin is part of.
Success result
The id of the Account that the plugin belongs to.
Timestamp when the plugin was created.
A security principal.
OAuth scope.
The default group a plugin belongs to.
Description of the plugin.
Is plugin enabled.
Timestamp when the plugin was most recently used.
Timestamp when the plugin was most recently updated.
If a requester is updating/using a Plugin they must have the relevant permissions in all Groups that Plugin has access to. But for legacy Plugins, the requester is required to have relevant permissions in any one of the groups that Plugin has access to.
Name of the plugin, which must be unique within an account.
Unique id to identify a plugin.
Type of a plugin.
Plugin code that will be executed inside SGX enclave.
Language of plugin code.
Language of plugin code.
Set of all the groups that plugin is part of.