Kestra

Note: You need to use docker to perform some tasks in the workflow. If your network environment cannot access the default docker address, you need to modify yml to use other docker sources. For example, using containerImage to specify docker sources: ``` id: koala_747164 namespace: company.team tasks: - id: hello type: io.kestra.plugin.core.log.Log message: Hello World!🚀 - id: second_task type: io.kestra.plugin.scripts.shell.Commands containerImage: dockerproxy.net/library/alpine commands: - echo 666 ``` For specific usage methods, please refer to the official document: kestra.io/docs/getting-started/quickstart#start-kestra Language can be changed in settings Kestra is an open source event-driven orchestration platform that makes it easy to implement planning workflows and event-driven workflows. By introducing Infrastructure as Code (IaaS) best practices into data, process and microservice orchestration, you can build a reliable workflow directly from the UI with just a few lines of YAML code. ##Main functions: Everything is code and can be built from the UI: By integrating Git version control, you can keep the workflow coded even when the UI builds the workflow. Event-driven and planning workflows: With simple trigger definitions, planning workflows and real-time event-driven workflows can be automated. Declarative YAML interface: Workflow can be defined using simple configuration in the built-in code editor. Rich plug-in ecosystem: Hundreds of plug-ins are built in to extract data from any database, cloud storage or API and run scripts in any language. Intuitive UI and code editor: Build and visualize workflows directly from the UI with syntax highlighting, auto-completion, and real-time syntax verification. Scalable: Designed to handle millions of workflows with high availability and fault tolerance. Version-control-friendly: You can write workflows using a built-in code editor and push them directly from Kestra to your preferred Git branch, implementing best practices for CI/CD pipelines and version control systems. Structure and elasticity: Eliminate chaos and enhance the resilience of the workflow through namespaces, tags, subflows, retries, timeouts, error handling, inputs, output from generating artifacts in the UI, variables, conditional branching, advanced scheduling, event triggers, backfilling, dynamic tasks, sequential and parallel tasks, and skipping tasks or triggers by setting the flag to true. 🧑‍💻每当您从 UI 或通过 API 调用更改工作流时，YAML 定义都会自动调整。Therefore, even if you modify the workflow in other ways (UI, CI/CD, Terraform, API calls), orchestration logic is always managed declaratively in the code. Kestra is an open-source, event-driven orchestration platform that makes both scheduled and event-driven workflows easy. By bringing Infrastructure as Code best practices to data, process, and microservice orchestration, you can build reliable workflows directly from the UI in just a few lines of YAML. ## Key Features: Everything as Code and from the UI: keep workflows as code with a Git Version Control integration, even when building them from the UI. Event-Driven & Scheduled Workflows: automate both scheduled and real-time event-driven workflows via a simple trigger definition. Declarative YAML Interface: define workflows using a simple configuration in the built-in code editor. Rich Plugin Ecosystem: hundreds of plugins built in to extract data from any database, cloud storage, or API, and run scripts in any language. Intuitive UI & Code Editor: build and visualize workflows directly from the UI with syntax highlighting, auto-completion and real-time syntax validation. Scalable: designed to handle millions of workflows, with high availability and fault tolerance. Version Control Friendly: write your workflows from the built-in code Editor and push them to your preferred Git branch directly from Kestra, enabling best practices with CI/CD pipelines and version control systems. Structure & Resilience: tame chaos and bring resilience to your workflows with namespaces, labels, subflows, retries, timeout, error handling, inputs, outputs that generate artifacts in the UI, variables, conditional branching, advanced scheduling, event triggers, backfills, dynamic tasks, sequential and parallel tasks, and skip tasks or triggers when needed by setting the flag disabled to true. 🧑‍💻 The YAML definition gets automatically adjusted any time you make changes to a workflow from the UI or via an API call. Therefore, the orchestration logic is always managed declaratively in code, even if you modify your workflows in other ways (UI, CI/CD, Terraform, API calls).