Get started with Kestra in 4 minutes.
The official Kestra Blueprints library can be found under kestra.io/docs.
Blueprints are a curated, organized, and searchable catalog of ready-to-use examples designed to help you kickstart your workflow.
Each Blueprint combines code and documentation and can be assigned several tags for organization and discoverability.
- Make sure your flow id uses url-style-hyphen-case-notation.
- Make your flow id as long and descriptive as possible.
- Make sure that the file name matches the flow id of your blueprint.
Sanity checks in Kestra are test flows used to verify functionality of plugins and tasks:
Structure:
- Plugin sanity checks: Flow ID is the task name, namespace "sanitychecks", and include Assert tasks to test task outputs.
- Flow sanity checks: Flow ID mentions main tasks, namespace "sanitychecks", they tests complete workflow (always self-contained)
External Dependencies:
- OSS services: Use Docker Run/Stop tasks
- Cloud services: Leverage sandbox environments when possible
- SaaS/License services: Not currently supported (or hard coded credentials from demo accounts)
Organization:
- All sanity checks are synced to the blueprint repository
- Plugin checks: Located in plugin repos, pulled to blueprint repo via CI/CD
- Flow checks: Written directly in blueprint repo into the
sanitychecks/flows
folder. Blueprints withdemo: true
are also synced intosanitychecks/flows/blueprints
Please check the full Notion page for full information