Fuzzball Documentation
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Interacting with Other Users' Workflows

Workflows started by other members of your group are visible to you. To list them, widen the scope of fuzzball workflow list, which shows only your own workflows by default:

$ fuzzball workflow list --scope group

Listing is all that plain group membership grants. Reading a workflow’s logs, or running commands inside one of its jobs, requires ownership of that workflow. Group owners and organization owners already hold it over every workflow in their scope; everyone else has to be added. To let another group member act on a workflow you started, add them as an owner:

$ fuzzball workflow owner add WORKFLOW_ID user3@ciq.com
User "Jane Doe" added as workflow WORKFLOW_ID owner

The second argument takes either an email address or a user ID. Use the ID when an email is ambiguous – fuzzball group member list shows both for every member of your group:

$ fuzzball group member list
ID                                   | EMAIL         | PRIORITY
e554e134-bd2d-455b-896e-bc24d8d9f81e | user1@ciq.com | 0
c3037e4e-e84d-41c6-96a6-bb2f8c5515db | user2@ciq.com | 0
74a78835-1601-4364-a85c-0eee707b8017 | user3@ciq.com | 0
77a50121-b7a9-4092-8776-c4a932cbdcd6 | user4@ciq.com | 0
1b4f57da-9865-4975-bf17-259875ee065a | user5@ciq.com | 0

The new owner can view the workflow’s logs. While the workflow is still running, they can also run commands and open an interactive shell in its job containers.

Ownership is full control, not read-only access. An owner can also stop the workflow, change its priority, and add or remove other owners. Depending on how your cluster is configured, an owner may be able to delete it as well.

Run fuzzball workflow owner list WORKFLOW_ID to see who currently owns a workflow, and fuzzball workflow owner remove WORKFLOW_ID USER to revoke access.