Docs
amfelt template eject
Copy a target plugin’s SQL template into your project.
Writes the named plugin’s own copy of a SQL template into
templates/<plugin>/<template>.sql, so you start from SQL that already works
rather than from documentation. The copy is taken from the plugin version this
project is pinned to, so it matches what actually runs.
Only templates the plugin offers for customizing can be copied; ask the plugin what those are and it answers with the same list this command checks against, so the two can never disagree.
An existing file is never overwritten. Once a template is in your project it is yours, and replacing it with the plugin’s original would throw away the work this command exists to start. Delete it yourself if you want to begin again.
Usage
amfelt template eject <plugin> <template> [flags]Examples
template eject target-postgres bridge
Copies the PostgreSQL bridge-view template into
templates/target-postgres/bridge.sql.
template eject target-duckdb scd2 --path pcf/PCF-duckdb.yaml
Copies the DuckDB history-merge template for the project defined by the given
project file.Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--path | string | amfelt.yaml | path of the Amfelt project file |
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 |
See also
template— the parent command
Generated from amfelt v5.6.3.
Last updated on November 1, 2026