m1yag1.globus.globus_flows module – Manage Globus Flows
Note
This module is part of the m1yag1.globus collection (version 0.6.0).
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install m1yag1.globus.
To use it in a playbook, specify: m1yag1.globus.globus_flows.
New in m1yag1.globus 1.0.0
Synopsis
Create, update, or delete Globus Flows
Deploy and manage workflow automation
Parameters
Parameter |
Comments |
|---|---|
Who can administer this flow. Accepts usernames (e.g., user@globusid.org), identity URNs, or group URNs. |
|
Authentication method to use. If not specified, auto-detects based on available credentials. When Otherwise falls back to Choices:
|
|
Globus Auth client ID for client_credentials authentication. Can also be set via the |
|
Globus Auth client secret for client_credentials authentication. Can also be set via the |
|
Flow definition (JSON or dict) |
|
Path to file containing flow definition |
|
Description of the flow |
|
ID of existing flow (for updates) |
|
Input schema for the flow |
|
Keywords for the flow |
|
Who can run this flow. Accepts usernames (e.g., user@globusid.org), identity URNs, group URNs, or special values. Special values include ‘public’ and ‘all_authenticated_users’. |
|
Desired state of the flow Choices:
|
|
Subscription ID for flow creation (required when user has multiple subscriptions) |
|
Subtitle of the flow |
|
Title of the flow |
|
Visibility settings for the flow. Accepts usernames (e.g., user@globusid.org), identity URNs, group URNs, or special values. Special values include ‘public’ and ‘all_authenticated_users’. |
Notes
Note
Authentication is required for all Globus API operations.
For
client_credentialsauth, register a confidential client at https://developers.globus.org.For
cliauth, runglobus loginfirst to cache tokens.The
climethod reads tokens from~/.globus/cli/storage.db.For
cliauth with multiple profiles, setGLOBUS_PROFILEenvironment variable.Set
GLOBUS_SDK_ENVIRONMENTtosandboxortestfor non-production environments.
See Also
See also
- Globus Auth Documentation
Official Globus authentication documentation
- Globus CLI
Command-line interface for Globus
Examples
- name: Create a Globus Flow
globus_flows:
title: "Data Processing Pipeline"
subtitle: "Automated data processing and analysis"
description: "Processes raw data through multiple stages"
definition:
Comment: "Simple data processing flow"
StartAt: "ProcessData"
States:
ProcessData:
Type: "Action"
ActionUrl: "https://compute.api.globus.org"
Parameters:
endpoint: "my-compute-endpoint"
function: "process_data"
End: true
keywords:
- "data-processing"
- "automation"
visible_to:
- "public"
runnable_by:
- "all_authenticated_users"
state: present
- name: Create flow from file
globus_flows:
title: "File Transfer Flow"
definition_file: "/path/to/flow_definition.json"
state: present
- name: Delete a flow
globus_flows:
title: "Old Flow"
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
Whether the flow was changed Returned: always |
|
ID of the created/managed flow Returned: when state=present |
|
Globus Auth scope for this flow (used for timers and external triggering) Returned: when state=present |
|
Title of the flow Returned: always |