App Component Templates
An Application Component Template is a reusable blueprint for creating new Application Components. It defines the component's technology stack, configuration properties, CI pipeline setup, and delivery defaults. When a developer creates a new component and selects a template, the component is scaffolded from the template's repository and pre-configured according to the template definition.
Templates are versioned and published — only published versions are available for component creation. Once published, a version is immutable; changes require publishing a new version.
Before creating your first template, it is recommended to familiarize yourself with how Templating works — it explains the Jinja-based engine, how to use property keys in file names and content, and how to prepare the template repository.
What You Can Do
| Action | Description |
|---|---|
| Browse templates | View, search, and filter all App Component Templates you have access to |
| View template detail | See repository status, template card, configuration preview, publish history, and component instances |
| Clone repository | Clone the template's Git repository for local development |
| Publish a new version | Release a new immutable version of the template available for component creation |
| Run a Dry Run | Validate the template by simulating component creation without persisting data |
| Edit | Edit the template — Template Card, Component Configuration, CI, Templating Rules, and CD |
| Manage permissions | Control who can view, edit, publish, or administer the template |