{"id":19207123,"url":"https://github.com/kestra-io/examples","last_synced_at":"2025-10-09T09:32:14.377Z","repository":{"id":162189997,"uuid":"636718826","full_name":"kestra-io/examples","owner":"kestra-io","description":"Best practices for data workflows, integrations with the Modern Data Stack (MDS), Infrastructure as Code (IaC), Cloud Provider Services","archived":false,"fork":false,"pushed_at":"2025-03-24T17:12:15.000Z","size":3444,"stargazers_count":25,"open_issues_count":0,"forks_count":9,"subscribers_count":7,"default_branch":"main","last_synced_at":"2025-04-21T09:06:48.778Z","etag":null,"topics":["analytics-engineering","automation","data-engineering","data-orchestration","data-pipelines","data-workflows","orchestration"],"latest_commit_sha":null,"homepage":"","language":"HCL","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/kestra-io.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2023-05-05T13:38:27.000Z","updated_at":"2025-03-24T17:12:18.000Z","dependencies_parsed_at":"2023-07-07T04:16:38.062Z","dependency_job_id":"b1c6ba96-f19e-4a17-98c9-d4d399793769","html_url":"https://github.com/kestra-io/examples","commit_stats":null,"previous_names":["kestra-io/examples"],"tags_count":0,"template":true,"template_full_name":null,"purl":"pkg:github/kestra-io/examples","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kestra-io%2Fexamples","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kestra-io%2Fexamples/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kestra-io%2Fexamples/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kestra-io%2Fexamples/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/kestra-io","download_url":"https://codeload.github.com/kestra-io/examples/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kestra-io%2Fexamples/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":279001135,"owners_count":26083022,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-10-09T02:00:07.460Z","response_time":59,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["analytics-engineering","automation","data-engineering","data-orchestration","data-pipelines","data-workflows","orchestration"],"created_at":"2024-11-09T13:18:22.621Z","updated_at":"2025-10-09T09:32:14.360Z","avatar_url":"https://github.com/kestra-io.png","language":"HCL","readme":"# Data Orchestration with Kestra\n\nThis repository will:\n1. Help you **get started** with Kestra\n2. Provide examples of how to **use Kestra**\n3. Provide examples of how to **integrate** Kestra with Infrastructure as Code tools (Terraform, GitHub Actions), Modern Data Stack products, and public cloud provider services\n4. Share **best practices** for managing data workflows across environments so that moving from development to production is as easy as possible without sacrificing security or reliability\n\n## Video tutorials\n\n- Getting started video explaining key concepts: https://youtu.be/yuV_rgnpXU8\n- Managing development and production environments in Kestra: https://youtu.be/tiHa3zucS_Q\n\n---\n\n# How to install Kestra\n\nDownload the Docker Compose file:\n\n```sh\ncurl -o docker-compose.yml https://raw.githubusercontent.com/kestra-io/kestra/develop/docker-compose.yml\n```\n\nStart Kestra:\n\n```sh\ndocker-compose up\n```\n\n![install.png](images/install.png)\n\n---\n\n# Hello-World example\n\nHere is a simple example logging hello world message to the terminal:\n\n```yaml\nid: hello  \nnamespace: prod\ntasks:\n  - id: hello-world\n    type: io.kestra.plugin.core.log.Log\n    message: Hello world!\n```\n\n## Adding a schedule\n\nHere is how you can add a schedule trigger to run the flow every minute: [helloParametrizedScheduled.yml](flows/getting_started/helloParametrizedScheduled.yml)\n\nTo add multiple schedules, each running with different input parameter values, use [helloParametrizedMultipleSchedules.yml](flows/getting_started/helloParametrizedSchedulesMultiple.yml)\n\n---\n\n# How to integrate Kestra with other tools in the Modern Data Stack \n\n## Airbyte\n\nHere is an example of using Kestra with Airbyte running in other Docker container: [airbyteSync.yml](flows/airbyte/airbyteSync.yml)\n\nAnd example running multiple Airbyte syncs in parallel: [airbyteSyncParallel.yml](flows/airbyte/airbyteSyncParallel.yml) \n\n## Fivetran\n\nHere is an example of a flow with a single task triggering a Fivetran sync: [fivetranSync.yml](flows/fivetran/fivetranSync.yml)\n\n---\n\n\n# Custom Scripts\n\n## How to run Bash and Python tasks\n\nHere is an example of a Bash task: [csvKit](flows/python/csvKit.yml)\n\n\n### Custom Docker image per task \n\nIf you prefer to run the Python or Bash task in a (_potentially custom_) Docker container: [pythonScriptContainer](flows/python/pythonScriptContainer.yml)\n\nUsing `dockerOptions` with the `dockerConfig` attribute, you can also configure credentials to private Docker registries:\n\n`auths: { \"my.registry.com\" : { auth: \"token\" } }`\n\n\n### Docker image with `requirements.txt` built at runtime \n\n\n```yaml\nid: hello_python_docker\nnamespace: company.team\ntasks:\n  - id: python_container\n    type: io.kestra.plugin.scripts.python.Script\n    beforeCommands:\n      - pip install requests pandas\n    taskRunner:\n      type: io.kestra.plugin.scripts.runner.docker.Docker\n    containerImage: python:3.11-slim\n    script: |\n      import pandas as pd\n      import requests\n      \n      print(pd.__version__)\n      print(requests.__version__)\n```\n\n\n## Keyboard shortcuts for the built-in editor in the UI\n\nOn Mac:\n- fn + control + Space = Autocomplete\n- command + K + C = Comment\n- command + K + U = Uncomment\n- opt + up/down = Move line up/down\n\nOn Windows:\n- ctrl + space = Autocomplete\n- ctrl + K + C = Comment\n- ctrl + K + U = Uncomment\n- alt + up/down = Move line up/down\n\n---\n\n# Credentials management\n\n## Open-source Kestra\n\nIn the open-source version, you can leverage Secrets.\n\nCreate an `.env` file and add any environment variables there with the prefix `SECRET_`, as shown in the [.env_example](.env_example) file. The values are the passwords in the base64 encoded format.\n\nThen, you can reference the secrets in your flow using `{{ secret('AIRBYTE_PASSWORD') }}`. Note that we drop the `SECRET_` prefix while referencing the secrets.\n\nFor security reasons, environment variables are fixed at the application startup (JVM startup).\n\nAlso, make sure that your Kestra container contains this configuration in your [docker-compose.yml](docker-compose.yml) file:\n\n```yaml\n  kestra:\n    image: kestra/kestra:develop-full\n    ...\n    env_file:\n      - .env\n    environment:\n      KESTRA_CONFIGURATION: |\n        kestra:\n          ...\n```\n\n## Cloud \u0026 Eneterprise Edition\n\nCloud \u0026 Enterprise Editions have a dedicated credentials managers with extra encryption, namespace-bound credential inheritance hierarchy and an RBAC-setting behind it.\n\nYou can add a Secret in the relevant namespace from the Namespace tab in the UI. You should not add the `SECRET_` prefix while setting up the secrets via the Namespace tab.\n\nTo reference that secret in your flow, use `{{ secret('AWS_ACCESS_KEY_ID') }}`.\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkestra-io%2Fexamples","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fkestra-io%2Fexamples","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkestra-io%2Fexamples/lists"}