Skip to main content

qwenpaw-data-cli

Standalone command-line interface for QwenPaw Data.

This package provides the qwenpaw-data command and connects local host workflows through qwenpaw-data-host-core.

The command automatically loads QWENPAW_DATA_ENV_FILE when set. Otherwise, an editable checkout is discovered from the CLI package location and the repository root .env is loaded. Existing process environment variables take precedence over dotenv values. Outside an editable checkout, the current working directory is used as the fallback configuration root.

Available command groups:

  • plan
  • execute
  • run
  • chat
  • datasource
  • semantic
  • doctor

Run qwenpaw-data doctor before the first task to check supported Python/Node versions, uv, model and authentication configuration, QwenPaw Data Home, DataBridge MCP, Docker, Neo4j, and the DataBridge API. qwenpaw-data doctor --json emits a machine-readable report that reports whether credentials are set without printing their values.

datasource manages the datasources configured in DataBridge:

qwenpaw-data datasource list
qwenpaw-data datasource get <datasource_id> [--show-config]
qwenpaw-data datasource create --name <n> --type <t> \
  (--config-file <f.json> | --config '<json>') [--test]
qwenpaw-data datasource update <datasource_id> [--name <n>] [--type <t>] [--config-file <f>]
qwenpaw-data datasource delete <datasource_id> [--yes]
qwenpaw-data datasource test (<datasource_id> | --type <t> --config-file <f>)

Set QWENPAW_DATA_CM_BASE_URL to the DataBridge origin. It defaults to http://127.0.0.1:8765. Every command emits JSON and masks saved passwords, AccessKeys, and STS tokens before writing anything to stdout; there is no option that prints stored credentials. list uses the credential-free discovery endpoint, while the management subcommands call the /api/semantic-config routes and need an API key with the credentials:manage scope when scoped keys are configured (QWENPAW_DATA_CLIENT_API_TOKEN or QWENPAW_DATA_API_TOKEN).

semantic manages the DataBridge semantic configuration layer. The seven resources domain, dataset, column, dimension, binding, metric, and formula share the same verbs:

qwenpaw-data semantic <resource> list [filters] [--page N --size N | --all]
qwenpaw-data semantic <resource> get <id>
qwenpaw-data semantic <resource> create (field flags | --file payload.json)
qwenpaw-data semantic <resource> update <id> (field flags | --file payload.json)
qwenpaw-data semantic <resource> delete <id> [--yes]

binding and formula also support dataset-level batch deletion with delete --dataset-id <id>. Reads require the query scope and writes the manage scope. Two more subcommands cover import and publishing:

# Import a semantic configuration workbook into the draft store
qwenpaw-data semantic import --file demo_semantic_config.xlsx

# Publish (weave) the configuration into the graph store
qwenpaw-data semantic weave submit --datasource-id <id> [--mode FULL] [--wait]
qwenpaw-data semantic weave list [--datasource-name <n>] [--task-name <n>]
qwenpaw-data semantic weave kill <task_id>

With --wait the CLI polls until the task reaches a terminal state (success, failed, killed), printing progress to stderr and the final task record as JSON to stdout; the exit code is 0 only for success.

The default CLI model uses provider openai together with LLM_MODEL, OPENAI_API_KEY, and OPENAI_BASE_URL. Set the corresponding QWENPAW_DATA_MODEL_PROVIDER, QWENPAW_DATA_MODEL_NAME, QWENPAW_DATA_MODEL_API_KEY, and QWENPAW_DATA_MODEL_BASE_URL variables to override individual values for the CLI.

Output and logs

The CLI writes streamed agent events, final answers, and execution summaries to stdout. Interactive prompts and concise command errors remain explicit CLI output on the terminal rather than raw log records. Python logging is written to ${QWENPAW_DATA_HOME}/host/qwenpaw_data.log at INFO level and above; QWENPAW_DATA_HOME defaults to ~/.qwenpaw-data.

The log rotates at 50 MB and keeps two backups as qwenpaw_data.log.1 and qwenpaw_data.log.2. Rotation assumes one active CLI process per QWENPAW_DATA_HOME. Direct users of qwenpaw-data-host-core continue to own their process logging configuration.

This package intentionally omits serve and local initialization helpers from the public CLI help.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

qwenpaw_data_cli-0.1.0.tar.gz (34.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

qwenpaw_data_cli-0.1.0-py3-none-any.whl (31.9 kB view details)

Uploaded Python 3

File details

Details for the file qwenpaw_data_cli-0.1.0.tar.gz.

File metadata

  • Download URL: qwenpaw_data_cli-0.1.0.tar.gz
  • Upload date:
  • Size: 34.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.7.14

File hashes

Hashes for qwenpaw_data_cli-0.1.0.tar.gz
Algorithm Hash digest
SHA256 6979ed5a96db1ce8ed3d8eadacc73c75a058841531bac25f7aab96bc5b9aa7b7
MD5 c1154a14cd8f5dd0dfd7d202cab0d0a4
BLAKE2b-256 d696ea5b54b9a8e5030995cb7a9ac1afe939c828e9236bea01b17dff6715dcbd

See more details on using hashes here.

File details

Details for the file qwenpaw_data_cli-0.1.0-py3-none-any.whl.

File metadata

File hashes

Hashes for qwenpaw_data_cli-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 07a640f7bd9a594222ed95117982ed178ca114725692f6f4c9da779a8fc84e83
MD5 1ad2ccc9a19da2b37d7d4d8b8b9cd4fa
BLAKE2b-256 e384f5b619cbc08a16bb5923ee387554726e4680de3b89fdfe872acc7ec014d1

See more details on using hashes here.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 files

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page