Self-Service Actions
Self-Service Action Descriptor
Regardless of whether you're using UI editing or GitOps to manage your self-service actions, the definitions are backed by JSON files. Each file is a fully compliant OpenAPI 3 spec file, with our own specific extensions.
All automation rule descriptors have 5 metadata fields:
ID: A unique identifier for the rule.
Name: A user-friendly display name.
Description (Optional): A concise overview of the action for further context.
Is Active: Boolean parameter that determines whether the self-service-action is active and should be executed or not.
Type: Defines the type of rule (
selfServiceAction
) .
Triggers
Triggers are conditions that initiate the execution. For self-service actions, the only available trigger type is manual
meaning users need to manual execute the action either via the UI or API.
The trigger sections also specify the arguments (and their data-types) that a self-service action requires to be triggered, which are used as input when triggering an action from the UI.
E.g.
Actions
Data Manipulation
Example 1 (Creating a Gitlab Repository)
Learn More
Last updated
Was this helpful?