# Forge flags

In order to reduce the amount of configuration required to integrate a pipeline into a deployment template, a standard deployment template application runs the primary and partial update Forge processes with an abbreviated set of flags.

Since the deployment template already specifies directory structures and file prefixes, the following flags are used to override a pipeline's input and output components, specifying the appropriate directories and prefixes for either reading or writing data.

## Primary Forge flags

Flag | Description
--- | ---
`--inputDir` | [appdir]/data/processing
`--stateDir` | [appdir]/data/state
`--tmpDir` | [appdir]/data/forge_temp
`--logDir` | [appdir]/logs/baseline
`--outputDir` | [appdir]/data/forge_output
`--outputPrefix` | [dataPrefix]

## Partial update Forge flags

Flag | Description
--- | ---
`--inputDir` | [appdir]/data/partials/processing
`--stateDir` | [appdir]/data/state
`--tmpDir` | [appdir]/data/forge_temp
`--logDir` | [appdir]/logs/partial
`--outputDir` | [appdir]/data/partials/forge_output
`--outputPrefix` | [dataPrefix]