OverviewArchitectureRecipeSourceProcessorSinkContext Graph for AI
OverviewArchitectureRecipeSourceProcessorSinkContext Graph for AI

Commands

Meteor supports the following commands:

  • run: Execute recipes for metadata extraction.
  • lint: Validate recipe files for errors.
  • recipe init: Bootstrap a new recipe.
  • recipe gen: Generate multiple recipes from a template.
  • plugins list: List available extractors, sinks, and processors.
  • plugins info: Display detailed information about a plugin.
  • entities: List entity types across all extractors.
  • edges: List edge types across all extractors.
  • version: Print the Meteor version.

Running recipes

# run a single recipe
meteor run recipe.yaml

# run all recipes in the specified directory
meteor run recipes/

# run all recipes in the current directory
meteor run .

# preview extracted records without sending to sinks
meteor run recipe.yaml --dry-run

# extract only the first 10 records for testing
meteor run recipe.yaml --dry-run --limit 10

# override log level for debugging
meteor run recipe.yaml --log-level debug

# use a custom config file
meteor run recipe.yaml --config /path/to/meteor.yaml

# pass recipe variables from a file
meteor run recipe.yaml --var secrets.yaml

A directory run reads every file in the directory (it does not recurse into subdirectories) and runs all recipes in parallel. Files that fail to parse are skipped with a warning. Variables from --var override METEOR_ environment variables.

Flags

FlagShortDefaultDescription
--config-c./meteor.yamlFile path for agent-level config
--varPath to a YAML file with recipe variables
--log-levelOverride log level (debug, info, warn, error)
--dry-runfalseExtract records without sending to sinks
--limit0Maximum number of records to extract (0 = unlimited)

Linting recipes

# validate a single recipe
meteor lint recipe.yaml

# lint all recipes in the specified directory
meteor lint recipes/

# lint all recipes in the current directory
meteor lint .

# lint with debug logging
meteor lint recipe.yaml --log-level debug

Lint checks the recipe version, that every named plugin exists, and that each plugin's config is valid. Note that lint reads METEOR_ environment variables only; it has no --var flag.

Flags

FlagDefaultDescription
--log-levelOverride log level (debug, info, warn, error)

Creating sample recipes

# bootstrap a recipe with a bigquery extractor and a console sink
meteor recipe init sample -n mycompany -e bigquery -s console

# bootstrap a recipe with multiple sinks and a processor
meteor recipe init sample -n mycompany -e bigquery -s compass,kafka -p enrich

# save the generated recipe to a file
meteor recipe init sample -n mycompany -e postgres -s console > recipe.yaml

# interactive mode (prompts for extractor, sinks, processors)
meteor recipe init sample -n mycompany

The generated recipe includes each plugin's sample config, printed to stdout.

Flags

FlagShortRequiredDescription
--scope-nYesURN namespace for the recipe
--extractor-eNoExtractor to use (interactive if omitted)
--sinks-sNoComma-separated list of sinks (interactive if omitted)
--processors-pNoComma-separated list of processors (interactive if omitted)

Generating multiple recipes

# generate multiple recipes from a template
meteor recipe gen template.yaml -d data.yaml -o ./output-dir

The data file is a YAML list of entries, each with a FileName and Data map. Meteor writes one recipe per entry into the output directory, filling the template with that entry's data.

Flags

FlagShortDescription
--output-oOutput directory
--data-dTemplate data file

Listing plugins

# list all available plugins (extractors, sinks, processors)
meteor plugins list

# list only extractors
meteor plugins list --type extractor

# list only sinks
meteor plugins list --type sink

# list only processors
meteor plugins list --type processor

# filter extractors by entity type
meteor plugins list --entity-type table

# filter extractors by edge type
meteor plugins list --edge-type derived_from

# filter extractors by tag
meteor plugins list --tag gcp

# output as JSON for scripting
meteor plugins list --format json

Flags

FlagShortDefaultDescription
--typeFilter by plugin type (extractor, sink, processor)
--entity-typeFilter extractors by entity type
--edge-typeFilter extractors by edge type
--tagFilter extractors by tag
--format-ftableOutput format (table, json)

Getting plugin information

# display information about a plugin
meteor plugins info bigquery
meteor plugins info compass
meteor plugins info enrich

# show full markdown documentation
meteor plugins info bigquery --full

# output as JSON
meteor plugins info bigquery --format json

# interactive mode (prompts for plugin selection)
meteor plugins info

Flags

FlagShortDefaultDescription
--fullfalseShow full markdown documentation
--format-ftableOutput format (table, json)

Listing entity types

# list all entity types and which extractors produce them
meteor entities

# output as JSON
meteor entities --format json

Flags

FlagShortDefaultDescription
--format-ftableOutput format (table, json)

Listing edge types

# list all edge types and which extractors produce them
meteor edges

# output as JSON
meteor edges --format json

Flags

FlagShortDefaultDescription
--format-ftableOutput format (table, json)

Getting help

# general help
meteor --help

# help for a specific command
meteor run --help
meteor plugins list --help
StencilConfiguration
On this page
Running recipesFlagsLinting recipesFlagsCreating sample recipesFlagsGenerating multiple recipesFlagsListing pluginsFlagsGetting plugin informationFlagsListing entity typesFlagsListing edge typesFlagsGetting help