> V1.0.6 > Commands > Plakar pkg manifest.yaml
Version v1.0.6

pkg-manifest.yaml

PLAKAR-PKG-MANIFEST.YAML(5) File Formats Manual PLAKAR-PKG-MANIFEST.YAML(5)

manifest.yaml — Manifest for plugin assemblation

The manifest.yaml file format describes how to package a plugin. No build or compilation is done, so all executables and other files must be prepared beforehand.

manifest.yaml must have a top-level YAML object with the following fields:

The name of the plugins
The displayed name in the UI.
A short description of the connectors.
A link to the homepage.
The license of the connectors.
A YAML array of strings for tags that describe the connectors.
The API version supported.
The plugin version, which doubles as the git tag as well. It must follow semantic versioning and have a ‘v’ prefix, e.g. ‘v1.2.3’.
A YAML array of objects with the following properties:
The connector type, one of importer, exporter, or store.
An array of YAML strings containing all the protocols that the connector supports.
An optional array of YAML strings describing some properties of the connector. These properties are:
Whether paths given to this connector have to be made absolute.
Whether this store backend handles a Kloset in a sigle file, for e.g. a ptar file.
Path to the plugin executable.
An optional array of YAML string. These are extra files that need to be included in the package.

A sample manifest for the “fs” plugin is as follows:

# manifest.yaml
name: fs
display_name: file system connector
description: file storage but as external plugin
homepage: https://github.com/PlakarKorp/integration-fs
license: ISC
tags: [ fs, filesystem, "local files" ]
api_version: 1.0.0
version: 1.0.0
connectors:
- type: importer
  executable: fs-importer
  protocols: [fs]
- type: exporter
  executable: fs-exporter
  protocols: [fs]
- type: storage
  executable: fs-store
  protocols: [fs]

plakar-pkg-create(1)

Plakar July 20, 2025 PLAKAR-PKG-MANIFEST.YAML(5)