DEVELOPERS DOCS

Home
Keboola Overview
- Our APIs
- Encryption
Extending Keboola
Integration
Automation/Common Tasks
CLI
- Installation
- Getting Started
- Structure
- Commands
  - help
  - status
  - sync
    - init
    - pull
    - push
    - diff
  - ci
    - workflows
  - local
    - create
      - config
      - row
    - persist
    - encrypt
    - validate
      - config
      - row
      - schema
    - fix-paths
    - template
      - delete
      - list
      - use
  - remote
    - create
      - branch
      - bucket
      - table
    - file
      - download
      - upload
    - job
      - run
    - table
      - create
      - upload
      - download
      - preview
      - detail
      - import
      - unload
    - workspace
      - create
      - delete
      - detail
      - list
  - template
    - repository
      - init
    - create
    - describe
    - list
    - test
      - create
      - run
  - dbt
    - init
    - generate
      - profile
      - sources
      - env
- GitHub Integration
- DevOps Use Cases
- Templates
- dbt

Manifest Files Specification

A manifest file contains additional information about tables and files injected to the /data/in folders. It also provides a way to specify options for tables and files transferred back to Storage from /data/out folders. Manifest files have the .manifest suffix to the original file.

All files in /data/in have the manifest file generated by us. For files generated by your code in /data/out, the manifest file is recommended. Also, keep in mind that all manifests have a lower priority than input and output mapping.

Format

The format of the manifest file is always JSON. The manifest file always has the .manifest extension. This applies to files with multiple extensions as well, so the following filenames are expected:

Data File Name	Manifest File Name
myfile	myfile.manifest
myfile.csv	myfile.csv.manifest
myfile.csv.gz	myfile.csv.gz.manifest

© 2024 Keboola