weevr-cli
CLI for managing weevr projects — scaffolding, validation, and deployment to Microsoft Fabric.
Documentation · Getting Started · CLI Reference
What it does
The weevr engine runs inside Fabric notebooks; the CLI runs on your workstation and in CI/CD pipelines.
weevr init— scaffold a new projectweevr new— generate thread, weave, loom, and warp files from templatesweevr validate— check files with the weevr engine's own loader and plannerweevr deploy— sync files to a Fabric Lakehouse via the OneLake APIweevr status— diff local files against deployed stateweevr list— view project structure, dependencies, and execution plansweevr plugins— manage CLI plugins
Installation
# With uv (recommended)
uv tool install weevr-cli
# With pipx
pipx install weevr-cli
# With pip
pip install weevr-cli
Quick Start
weevr init my-project --examples
cd my-project.weevr
weevr new thread orders
weevr validate
weevr deploy --target dev
See the Getting Started guide for a full walkthrough.
Configuration
The CLI reads .weevr/cli.yaml for deploy targets. See the Configuration Reference for details.
Requirements
- Python 3.11 (matches Fabric Runtime 1.3)
- Azure CLI (
az login) or equivalent credential for deploy/status commands
Development
See CONTRIBUTING.md for the full development guide.
License
Apache 2.0 — see LICENSE for details.
1 maintainer
Metadata
1 maintainer
Release files for weevr-cli 2.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| weevr_cli-2.0.1.tar.gz | 45.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| weevr_cli-2.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 108.0 kB
Release files / weevr_cli-2.0.1.tar.gz
| Download URL | weevr_cli-2.0.1.tar.gz |
|---|---|
| Size | 45.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63efb744d7da3575d7824576a1d805afb536074f3692e1df8320ac6dbbb171a6
|
|
BLAKE2b-256 checksum How to use checksums |
348e8a6c5eaa456820cb15ff6e912ce761c6592dd8e41d7ef1f755a6e810736c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / weevr_cli-2.0.1-py3-none-any.whl
| Download URL | weevr_cli-2.0.1-py3-none-any.whl |
|---|---|
| Size | 62.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6677efc0c38af1283d1642f47f5bdaa032f87acb6d413f69cd3ab8a3d24fa269
|
|
BLAKE2b-256 checksum How to use checksums |
0e5f22d46bbdc0b8d6baa40dae9856b8c36b88377275fdf69346828acbffd7d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for weevr-cli 2.0.1
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.
