Pyplines CLI

Deliver prepared automation and operate it through the public v1alpha1 Server API. The CLI needs neither Docker access nor the Action SDK.

pip install pyplines-cli
pyplines --server https://pyplines.example.com auth login --email you@example.com
pyplines --workspace operations install ./maintenance.tar.gz --config-file production.yaml
pyplines --workspace operations run restart-payments --input service=payments
pyplines --workspace operations logs restart-payments

For a fresh local development appliance, run from the repository root:

pyplines --server http://127.0.0.1:18085 bootstrap \
  --bootstrap-token-file .local/docker/pyplines-bootstrap-token
pyplines auth whoami
pyplines list

Bootstrap prompts for a Workspace, administrator email, and confirmed password, then saves the session and selects that Workspace. The CLI reads only the token file, never .local/docker/pyplines.env or other appliance settings. Supply the Server address with --server or PYPLINES_SERVER_URL. Bootstrap checks its status before prompting: if already complete, it reports that no changes were made and exits successfully. It never resets an existing installation.

For other installations, supply the token using --bootstrap-token-file or PYPLINES_BOOTSTRAP_TOKEN, or enter it at the hidden prompt. No token/password value flags are provided. For noninteractive use:

pyplines --server https://pyplines.example.com bootstrap \
  --email you@example.com --workspace operations \
  --bootstrap-token-file /secure/bootstrap-token \
  --password-file /secure/admin-password --json

Keep these input files private (for example, mode 0600 on Unix). Only the session is saved locally, not the bootstrap token or password. A lost connection can occur after bootstrap commits: try login before retrying. Successful initialization is not rolled back if saving the local session fails.

Password login creates a managed session under ~/.pyplines/credentials/. Passwords are not saved. Use PYPLINES_ACCESS_TOKEN for ServiceAccount automation, --json for structured output, and run -d for detached execution. auth logout revokes the saved session.

Requires the Docker v1alpha1 Server with migrations through 20260910000800. It does not support the retired Core/Project API. Upgrading the package replaces the old command surface; legacy credentials are not imported automatically.

pyplines version reports the installed CLI package version (including editable development suffixes) without connecting to the Server. Use pyplines version --json for structured output; this is the client version, not the Server version.

Commands: version, bootstrap, inspect, config, install, update, upgrade, uninstall, list, status, run, logs, runs list|wait|cancel, and auth login|whoami|logout. Configuration files use JSON-compatible YAML. Human-readable static text is the default; automation never encounters implicit prompts. Explicit login requires a terminal. Approvals and missing inputs are handled through authorized Page/API interactions, not CLI prompts.

See operation details for delivery semantics, limits, authentication, and qualification. The old cli/ sources are historical reference only and are excluded from both wheel and source distribution.

Download files

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

Source Distribution

pyplines_cli-2026.9.2a7.tar.gz (113.1 kB view details)

Uploaded Sep 10, 2026 Source

Built Distribution

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

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

pyplines_cli-2026.9.2a7-py3-none-any.whl (41.5 kB view details)

Uploaded Sep 10, 2026 Python 3

File details

Details for the file pyplines_cli-2026.9.2a7.tar.gz.

File metadata

Download URL: pyplines_cli-2026.9.2a7.tar.gz
Upload date: Sep 10, 2026
Size: 113.1 kB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for pyplines_cli-2026.9.2a7.tar.gz
Algorithm	Hash digest
SHA256	`386a4c41ce866a5d67f5e3cd9601dc51d6c7bfd5e314b2f5494cb51aa99cd773`
MD5	`c9fac97d1dc1019eb7fac6293cfa3d8d`
BLAKE2b-256	`b0f6b3020cb631f230e171da4374117c4cc0e121114b7731687111452acf09c8`

See more details on using hashes here.

Provenance

The following attestation bundles were made for pyplines_cli-2026.9.2a7.tar.gz:

Publisher: publish-release.yml on pyplines/pyplines

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: pyplines_cli-2026.9.2a7.tar.gz
- Subject digest: 386a4c41ce866a5d67f5e3cd9601dc51d6c7bfd5e314b2f5494cb51aa99cd773
- Sigstore transparency entry: 2787217908
- Sigstore integration time: Sep 10, 2026
Source repository:
- Permalink: pyplines/pyplines@11cefc0763d31e65a677cb0475e3194cf9e1831e
- Branch / Tag: refs/tags/v2026.9.2a7
- Owner: https://github.com/pyplines
- Access: private
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: publish-release.yml@11cefc0763d31e65a677cb0475e3194cf9e1831e
- Trigger Event: push