# amfelt template

Customize the SQL a target plugin generates.

Take a copy of the SQL templates a target plugin uses to build the warehouse
layers, change them to suit your warehouse, and check them before they run. A
copied template lives in your own repository alongside the project file, so it
is reviewed, versioned and reverted like any other source you own.

Templates you have not copied are unaffected — the plugin keeps using its own. A
copy that cannot be parsed, or that relies on something the template context
does not offer, stops the pipeline run rather than being quietly ignored, so a
template you changed is either the one that runs or the reason the run stopped.

## Usage

```text
amfelt template [command] [flags]
```

## Global flags

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--amfelt-dir` | `string` | `.amfelt` | directory for workspace files (such as plugins); does not move agent identity (controlled by AMFELT_DIR) |
| `--config` | `string` | — | directory or filename of the application configuration |
| `-f`, `--format` | `string` | `default` | log format to use; either default, pretty, or json |
| `-l`, `--level` | `string` | `info` | minimum log level to display; either error, warn, info, or debug |
| `-v`, `--verbose` | `bool` | `false` | trigger to use verbose logging |
{.clidoc-flags-table}

## Subcommands

- [`template eject`](/docs/reference/command-line/template-eject/)
- [`template validate`](/docs/reference/command-line/template-validate/)

---

Generated from `amfelt` v5.6.3.