Skip to main content

noetl-cli (v2.5.2)

Command-line interface for NoETL workflow automation framework.

About

noetl-cli is a Rust-based CLI that provides a fast, native interface to NoETL's workflow automation capabilities. It's distributed as a separate Python package using maturin, making the noetl command available on PATH.

Installation

Install NoETL with CLI support:

uv pip install "noetl[cli]"
# or with pip
pip install "noetl[cli]"

Standalone

Install just the CLI:

uv pip install noetl-cli
# or with pip
pip install noetl-cli

Development Build

Build and place the binary in the project's bin/ directory:

task noetlctl:local:build

Install to ~/.local/bin/:

task noetlctl:local:install
cargo build --release

The binary will be available at target/release/noetl.

Usage

Check version:

noetl --version

Server Management

Start NoETL server:

noetl server start
noetl server start --init-db  # Initialize database on startup

Stop NoETL server:

noetl server stop
noetl server stop --force  # Force stop without confirmation

Worker Management

Start NoETL worker (v2 event-driven architecture):

noetl worker start
noetl worker start --max-workers 4
noetl worker start --max-workers 8

Stop NoETL worker:

noetl worker stop  # Interactive selection if multiple workers
noetl worker stop --name my-worker
noetl worker stop --name my-worker --force

Database Management

Initialize database schema:

noetl db init

Validate database schema:

noetl db validate

Build Management

Build NoETL Docker image:

noetl build
noetl build --no-cache  # Build without using cache

The build command:

  • Builds the Docker image with a timestamp-based tag
  • Saves the tag to .noetl_last_build_tag.txt for deployment use
  • Streams build output to console
  • Replaces task docker-build-noetl

Kubernetes Management

Deploy NoETL to kind cluster:

noetl k8s deploy

Remove NoETL from cluster:

noetl k8s remove

Rebuild and redeploy:

noetl k8s redeploy
noetl k8s redeploy --no-cache  # Rebuild without cache

Full reset (schema reset + redeploy + test setup):

noetl k8s reset
noetl k8s reset --no-cache  # Reset with clean build

The k8s commands:

  • deploy: Applies Kubernetes manifests to kind cluster
  • remove: Deletes NoETL resources from cluster
  • redeploy: Builds image, loads to kind, and deploys (replaces task noetl:k8s:redeploy)
  • reset: Full workflow - resets database schema, redeploys, runs test setup (replaces task noetl:k8s:reset)

Configuration and Contexts

noetl supports multiple contexts to manage different server environments.

Add a Context

noetl context add local --server-url http://localhost:8082 --set-current
noetl context add prod --server-url http://noetl-server:8082

List Contexts

noetl context list

Switch Context

noetl context use prod

Show Current Context

noetl context current

CLI Mode

Catalog Management

Register a resource (auto-detects kind: Credential or Playbook):

noetl catalog register tests/fixtures/playbooks/data_transfer/http_to_postgres_transfer/http_to_postgres_transfer.yaml

Get resource details:

noetl catalog get tests/fixtures/playbooks/data_transfer/http_iterator_save_postgres

List resources:

noetl catalog list Playbook --json

Execution

Execute a playbook:

noetl execute playbook tests/fixtures/playbooks/regression_test/master_regression_test --json

Get execution status:

noetl execute status 522107710393811426 --json

Credentials

Get credential details:

noetl get credential gcs_service_account --include-data

SQL Query Execution

Execute SQL queries via NoETL Postgres API:

# Query with table format (default)
noetl query "SELECT * FROM noetl.keychain LIMIT 5"

# Query with specific schema
noetl query "SELECT execution_id, credential_name FROM noetl.keychain WHERE execution_id = 12345" --schema noetl

# Query with JSON output
noetl query "SELECT * FROM noetl.event ORDER BY created_at DESC LIMIT 10" --format json

# Query public schema tables
noetl query "SELECT * FROM users LIMIT 5" --schema public --format table

Output Formats:

  • table (default): Formatted ASCII table with borders
  • json: Pretty-printed JSON output

Example Output (table format):

┌────────────────────┬────────────────┬──────────────┐
│ execution_id       │ credential_name│ access_count │
├────────────────────┼────────────────┼──────────────┤
│ 507861119290048685 │ openai-api-key │ 0            │
│ 507861119290048686 │ postgres-creds │ 2            │
└────────────────────┴────────────────┴──────────────┘
(2 rows)

Registering (Legacy/Explicit)

Register a Credential:

noetl register credential -f tests/fixtures/credentials/pg_k8s.json

Register a Playbook:

noetl register playbook -f tests/fixtures/playbooks/api_integration/auth0/provision_auth_schema.yaml

Direct Execution/Status/List

Execute a Playbook:

noetl run playbook api_integration/auth0/provision_auth_schema

Get Execution Status:

noetl status <execution_id>

List Resources:

noetl list Playbook

Interactive TUI Mode

Run noetl with the -i or --interactive flag:

noetl --interactive
  • Navigation: Use Up/Down arrows or j/k to navigate lists.
  • Refresh: Press r to refresh the data.
  • Quit: Press q to exit.

Docker Integration

The noetl binary is built into the Docker image using a multi-stage build:

# Rust builder stage compiles the CLI
FROM rust:1.75-slim as rust-builder
WORKDIR /build
COPY noetlctl/ ./
RUN cargo build --release

# Production stage includes the binary
COPY --from=rust-builder /build/target/release/noetl /usr/local/bin/noetl

The Kubernetes manifests use the Rust CLI for server and worker management:

Server deployment:

command: ["noetl"]
args: ["server", "start"]

Worker deployment:

command: ["noetl"]
args: ["worker", "start"]

This provides a unified binary for both local development and containerized deployments.

Command Mapping

The Rust CLI replaces several task commands:

Task Command noetl Command
task docker-build-noetl noetl build
task noetl:k8s:deploy noetl k8s deploy
task noetl:k8s:redeploy noetl k8s redeploy
task noetl:k8s:reset noetl k8s reset
task noetl:server:start noetl server start
task noetl:worker:start noetl worker start

Metadata

Release files for noetl-cli 2.5.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for noetl-cli 2.5.3
File Size Uploaded Provenance Actions
noetl_cli-2.5.3.tar.gz 39.9 kB Without provenance Details for noetl_cli-2.5.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for noetl-cli 2.5.3
File Interpreter ABI Platform Actions
noetl_cli-2.5.3-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details for noetl_cli-2.5.3-py3-none-macosx_11_0_arm64.whl

Total release size: 2.6 MB

Release files / noetl_cli-2.5.3.tar.gz

Download URL noetl_cli-2.5.3.tar.gz
Size 39.9 kB
Tags Source
SHA-256 checksum
How to use checksums
c76221bf00259a6317baee58c7b72ffbb1548363ca35cd1fc77bde2a9f8a9427
BLAKE2b-256 checksum
How to use checksums
c853356f655603fd860bdad49b0790b09e6ef3bb5d5565144cea93c83f623aea
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.11.4

Release files / noetl_cli-2.5.3-py3-none-macosx_11_0_arm64.whl

Download URL noetl_cli-2.5.3-py3-none-macosx_11_0_arm64.whl
Size 2.5 MB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
ed1a4ee80ca08e0728d35343a95956667d88d0850b00947bc722e96b5cfb89b7
BLAKE2b-256 checksum
How to use checksums
b70be04dd53c7ca8d5aa53fc84e180d37b3252eb5002ec57dcafe7634ac0869c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via maturin/1.11.4

Security for noetl-cli 2.5.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

2.5.3 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page