Docs

amfelt add job

Add a job to the project configuration.

Usage  

amfelt add-job [name] [flags]

Flags  

FlagTypeDefaultDescription
--excludestring—object exclusion glob(s) for a select job; comma-separated
--forceboolfalseignore warnings and errors
--history-modestringscd2history table accumulation strategy; one of scd2, snapshot, append, scd1
--includestring—object selection glob(s) over the source contract for a select job; comma-separated (default *)
--layerstringallpipeline layer to deploy; one of staging, history, bridge, business, all
--pathstringamfelt.yamlpath of the Amfelt project file
--schedulestring—cron schedule for the select job’s run; empty means manual/dispatch-triggered
--schema-prefixstring—base schema prefix override (e.g. “myproject” → myproject_stg, myproject_hst); overrides the PCF’s job.schemaPrefix, falls back to “amfelt” if neither is set
--sourcestring—name of the source (must match a sources[].name in the project file)
--strategystringfullreplication strategy for a select job; one of full, incremental, cdc
--targetstring—name of the target (must match a targets[].name in the project file)
--write-modestring—write mode recorded for the job; one of append, upsert, replace. The agent does not apply it, because the staging layer is always replaced (truncate and reload) on every run. Leave this unset; use historyMode to control append or merge behavior at the history layer

Global flags  

FlagTypeDefaultDescription
--amfelt-dirstring.amfeltdirectory for workspace files (such as plugins); does not move agent identity (controlled by AMFELT_DIR)
--configstring—directory or filename of the application configuration
-f, --formatstringdefaultlog format to use; either default, pretty, or json
-l, --levelstringinfominimum log level to display; either error, warn, info, or debug
-v, --verboseboolfalsetrigger to use verbose logging

Generated from amfelt v5.6.3.


Last updated on November 1, 2026