veltro-cli
Stdlib-only operator CLI for the Veltro suite. Every Veltro release publishes it at the release's version. Install a release with:
curl -fsSL https://raw.githubusercontent.com/veltrosecurity/veltro/vX.Y.Z/install.sh \
| VELTRO_RELEASE=X.Y.Z sh -s -- --admin-email you@example.com
or pip install veltro-cli==X.Y.Z and veltro install --suite-version X.Y.Z.
Leave the version out to take the newest release.
While the repositories are private, GitHub answers 404 without a token. Export
VELTRO_GITHUB_TOKEN (GITHUB_TOKEN and GH_TOKEN work too) with a token
that can read veltrosecurity/veltro, and fetch the script with it:
curl -fsSL -H "Authorization: Bearer $VELTRO_GITHUB_TOKEN" …. install,
upgrade and status then read releases through the GitHub API, and the token
goes nowhere else. The images also need docker login ghcr.io with a
read:packages token.
veltro install asks for the first admin's email (--admin-email skips the
question and is required when there's no terminal). After the stack starts, the
admin's one-time sign-in link is in veltro logs veltro, on the line starting
First admin. For a locked-out admin, run
veltro admin reset --email you@example.com to print a fresh link
(--dry-run shows the Compose command it runs).
For an existing install with no bootstrap operator assignment, run
veltro operator-assign --email you@example.com with an enabled suite admin's
address. --dry-run checks email syntax and prints the Compose command. It doesn't
check whether the account exists, is enabled, or is an admin. Re-running prints the existing
operator's email without changing it. Identity delivers the assignment to
VectorFlow automatically and retries until ACK; bootstrapOperator.status
in the authenticated GET /api/suite/peer-reads response is ready when finished.
For Helm, use
kubectl -n <namespace> exec deploy/<release>-veltro-identity-server -- node operator-assign --email you@example.com.
Requires Python ≥ 3.10 and Docker Compose ≥ 2.20 on the host.
1 maintainer
Metadata
1 maintainer
Release files for veltro-cli 0.36.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| veltro_cli-0.36.6.tar.gz | 100.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| veltro_cli-0.36.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 216.3 kB
Release files / veltro_cli-0.36.6.tar.gz
| Download URL | veltro_cli-0.36.6.tar.gz |
|---|---|
| Size | 100.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7bc5fb37594502eb63504dc84095978b65ace174575c0279a86e9b235ab48827
|
|
BLAKE2b-256 checksum How to use checksums |
1429059b080281748e2413da12ea351c96531818e338b61ccf6e0e51fb7f0a6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logRelease files / veltro_cli-0.36.6-py3-none-any.whl
| Download URL | veltro_cli-0.36.6-py3-none-any.whl |
|---|---|
| Size | 116.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b6e1eb1cd305d5f7a5ceb4941c89c482390cd70a6558614aef68c54e51e1189
|
|
BLAKE2b-256 checksum How to use checksums |
0f4082f31216805234ed4ad9395bb7443e9345cc219371e1ef8abed98e0bed45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency log
