- Provides plugin components under
io.kestra.plugin.templates. - Includes classes such as
Example,Trigger.
- What user problem does this solve? Teams need a concrete starting point for building and validating new Kestra plugins without recreating the same project scaffolding from scratch.
- Why would a team adopt this plugin in a workflow? It gives plugin authors a ready-made reference repo they can adapt alongside their own build, test, and publishing workflow.
- What operational/business outcome does it enable? It shortens plugin delivery time, reduces setup mistakes, and makes internal or partner plugin development more repeatable.
Single-module plugin. Source packages under io.kestra.plugin:
templates
Infrastructure dependencies (Docker Compose services):
app
io.kestra.plugin.templates.Example
plugin-template/
├── src/main/java/io/kestra/plugin/templates/
├── src/test/java/io/kestra/plugin/templates/
├── build.gradle
└── README.md
- Base the wording on the implemented packages and classes, not on template README text.