# \[V1: deprecated] Workflow configuration file

A Workflow data operation is used to specify one or several data operation IDs that need to be successfully executed for one target data operation to be triggered.

## :eye\_in\_speech\_bubble: Example

```
{
  "configuration_type": "workflow",
  "configuration_id": "000099_iowa_liquor_workflow_export_cluster_stores",
  "environment": "DEV",
  "short_description": "Launch Iowa Liquor Tailer Demo Export Cluster Stores Tables",
  "account": "000099",
  "activated": true,
  "archived": false,
  "gcp_project_id": "fd-io-jarvis-demo-dlk",
  "authorized_job_ids": ["gbq-to-gbq|000099-build-iowa-liquor-model_DEV"],
  "target_dag": "table-to-storage",
  "extra_parameters": {
    "firestore_conf_doc_id": "000099_iowa_liquor_export_cluster_stores"
  }
}
```

## :gear: Parameters

| Parameter                                                                             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><strong>configuration\_type</strong></p><p>type: string</p><p>mandatory</p>        | <p>Type of configuration file.<br><br>In this case, the value has to be "workflow".</p>                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| <p><strong>configuration\_id</strong></p><p>type: string</p><p>mandatory</p>          | <p>ID of the workflow.</p><p>You can pick any name you want, but is has to be <strong>unique</strong> for this type of configuration file.</p><p>Note that in case of conflict, the newly deployed data operation will overwrite the previous one.</p>                                                                                                                                                                                                                                                                           |
| <p><strong>environment</strong></p><p>type: string</p><p>mandatory</p>                | <p>Deployment context.</p><p>Values: PROD, PREPROD, STAGING, DEV.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| <p><strong>short\_description</strong></p><p>type: string</p><p>optional</p>          | Short description of the context of the configuration file.                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| <p><strong>account</strong></p><p>type: string</p><p>mandatory</p>                    | Your account ID is a 6-digit number assigned to you by your Tailer Platform administrator.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| <p><strong>gcp\_project</strong></p><p>type: string</p><p>optional</p>                | ID of the Google Cloud project containing the BigQuery instance to be triggered.                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| <p><strong>gcp\_project\_id</strong></p><p>type: string</p><p>optional</p>            | Enter the same value as gcp\_project to avoid the question of project selection during a deployment with tailer deploy configuration command.                                                                                                                                                                                                                                                                                                                                                                                    |
| <p><strong>activated</strong></p><p>type: boolean</p><p>optional</p>                  | <p>Flag used to enable/disable the execution of the workflow.</p><p>If not specified, the default value will be "true".</p>                                                                                                                                                                                                                                                                                                                                                                                                      |
| <p><strong>archived</strong></p><p>type: boolean</p><p>optional</p>                   | <p>Flag used to enable/disable the visibility of the workflow's configuration and runs in Tailer Studio.</p><p>If not specified, the default value will be "false".</p>                                                                                                                                                                                                                                                                                                                                                          |
| <p><strong>authorized\_job\_ids</strong></p><p>type: string array</p><p>mandatory</p> | Data operations that need to be executed and successful for the current workflow to be triggered.                                                                                                                                                                                                                                                                                                                                                                                                                                |
| <p><strong>target\_dag</strong></p><p>type: string</p><p>mandatory</p>                | <p>Data operation to trigger.</p><p>For Tables to Tables data operations, you need to specify the data operation <strong>configuration\_id</strong>, concatenated with the environment ("\_PROD" or "\_DEV").</p><p>Example: "000099\_load\_stores\_details\_PROD"</p><p>For Storage to Storage, Storage to Tables et Table to Storage data operations, you only specify the type of data operation with one of the following values:</p><ul><li>storage-to-storage</li><li>storage-to-tables</li><li>table-to-storage</li></ul> |
| <p><strong>extra\_parameters</strong></p><p>type: dict</p><p>mandatory</p>            | <p>This array contains the list of data operations to trigger.</p><p>Leave it empty for Tables to Tables data operations, as the <strong>target\_dag</strong> parameter already contains this information.</p><p>For other data operations, list one or several <strong>firestore\_conf\_doc\_id</strong> parameters.</p>                                                                                                                                                                                                        |
| <p><strong>firestore\_conf\_doc\_id</strong></p><p>type: string</p><p>optional</p>    | <p>List of data operations to trigger.</p><p>Specify the <strong>configuration\_id</strong> of the data operations to trigger.</p>                                                                                                                                                                                                                                                                                                                                                                                               |