:zap: Workflow Automation Platform. Orchestrate & Schedule code in any language, run anywhere, 500+ plugins. Alternative to Zapier, Rundeck, Camunda, Airflow...
Some users want to extract some information from the kestra instance without interacting directly with the API, e.g. to:
fetch all flows
fetch all namespaces
download all flows, and all versions of specific flows.
Proposed Solution
We may provide dedicated core tasks for that:
ListFlows
ListNamespaces
DownloadFlows
Proposed syntax
ListNamespaces:
id: export_flows
namespace: dev
tasks:
- id: list
type: io.kestra.plugin.core.namespace.ListNamespaces
childNamespaces: true # true by default — whether to include flows from child namespaces
# outputs a list of strings
ListFlows:
id: list_flows
namespace: dev
tasks:
- id: list_flows
type: io.kestra.plugin.core.namespace.ListFlows
namespace: dev # only fetched from the current namespace by default
childNamespaces: true # true by default — whether to include flows from child namespaces
# outputs a list of strings
DownloadFlows:
id: export_flows
namespace: dev
tasks:
- id: export
type: io.kestra.plugin.core.namespace.DownloadFlows
namespace: dev # only fetched from the current namespace by default
childNamespaces: true # true by default — whether to include flows from child namespaces
pastRevisions: false # false by default — whether to include past revisions of each flow
# outputs ION with columns: namespace, flowId, revision, content. 1 row per flow
Problem
Some users want to extract some information from the kestra instance without interacting directly with the API, e.g. to:
Proposed Solution
We may provide dedicated core tasks for that:
Proposed syntax
ListNamespaces:
ListFlows:
DownloadFlows:
Workaround until then