Admin Commands

This page documents the administrator commands for managing catalog repositories. These commands provide additional capabilities beyond the standard user commands, including the ability to manage repositories system-wide and control individual application template availability.

These commands require administrative privileges in Fuzzball. Regular users should use the user commands instead.

Admin Catalog Repository Commands

Admin catalog repository commands are accessed under the fuzzball admin workflow-template catalog namespace.

Adding a Catalog Repository

Administrators can add catalog repositories with additional control over repository configuration:

$ fuzzball admin workflow-template catalog add <NAME> <URI> <BRANCH> [flags]

Arguments:

<NAME>: A descriptive name for the catalog repository
<URI>: The Git repository URI (HTTPS or SSH)
<BRANCH>: The branch to synchronize

Flags:

--owner-kind, -o: The owner type for the catalog repository (default: group)
- Options: group, organization, provider
--access-token, -t: Access token for private repositories
--id, -i: UUID to assign to this repository (optional)

Example - Add Organization-Wide Repository:

$ fuzzball admin workflow-template catalog add \
    "Official Catalog" \
    "https://github.com/example/official-catalog" \
    "main" \
    --id 22222222-2222-2222-2222-222222222222 \
    --owner-kind organization

Unlike the user import command, the admin add command does not automatically synchronize the repository. You must manually run reload after adding.

Reloading Catalog Repositories

Administrators can reload individual repositories or all repositories at once:

$ fuzzball admin workflow-template catalog reload [--all|<REPOSITORY_ID>]

Flags:

--all, -a: Reload all catalog repositories instead of a specific one

Example - Reload All Repositories:

$ fuzzball admin workflow-template catalog reload --all

Admin Workflow Template Commands

Administrators can enable or disable individual workflow templates to control their availability in the workflow catalog.

Enabling and Disabling a Workflow Template

To make a workflow template available in the catalog:

$ fuzzball admin workflow-template enable <TEMPLATE_ID>
$ fuzzball admin workflow-template disable <TEMPLATE_ID>

Example:

$ fuzzball admin workflow-template disable abc12345-6789-def0-1234-56789abcdef0

Disabled templates are not visible in the workflow catalog and cannot be used to create new workflows. Existing workflows created from the template are not affected.

Disabling templates is useful for:
Temporarily removing outdated or problematic templates without deleting them
Controlling which templates are available during maintenance periods
Managing template rollout and deprecation