Skip to main content

Anyscale

This package contains the command line interface and the sdk for the Anyscale platform.

View Anyscale docs here View CLI docs here View SDK docs here

Environment variables

ANYSCALE_LOG_STREAM

Selects the stream used for informational CLI and SDK output — progress messages, block headings and spinners. Accepts stderr (the default) or stdout; unrecognized values are treated as stderr. Warnings, errors and ANYSCALE_DEBUG output always go to stderr, whatever this is set to.

Set ANYSCALE_LOG_STREAM=stdout when a log collector classifies everything on stderr as an error — the GKE logging agent, for example — so that a normal deployment stops showing up as a failure.

Commands asked for a machine-readable payload (--json, --yaml, -o json, -o yaml) ignore this setting and keep informational output on stderr, so the payload on stdout stays parseable.

One thing to know before turning it on: informational output can contain sensitive values — tokens the CLI prints on purpose (anyscale service token add, anyscale service-account create) and anything echoed back from a config you pass in, including a workload's env_vars. Treat stdout as no less sensitive than stderr wherever the two are collected or retained differently.

ANYSCALE_EXTRA_HEADERS

Adds HTTP headers to every request the CLI and the Python SDK send to the Anyscale API, for example a token that a corporate reverse proxy in front of ANYSCALE_HOST requires. The value is a JSON object of header names to string values:

export ANYSCALE_EXTRA_HEADERS='{"X-Proxy-Token": "abc", "X-Team": "ml"}'

For a single command, pass --header 'Name: Value' before the command name, repeating it for more than one header:

anyscale --header 'X-Proxy-Token: abc' job list

In the SDK, anyscale.Anyscale(headers={...}) does the same for one client.

When more than one source sets a header of the same name, ignoring letter case, Anyscale(headers=...) wins over --header, which wins over ANYSCALE_EXTRA_HEADERS. Headers named in only one source are always sent.

  • The client sets Accept, Content-Length, Content-Type, Cookie, Host, Transfer-Encoding, traceparent, X-Anyscale-Client and X-Anyscale-Client-Version itself, so these names are rejected. Names must be HTTP tokens. Values must not be blank, and they can contain only printable ASCII characters and tabs.
  • Headers are read when a client is created. The CLI reads them once per command. In an SDK script, module-level calls such as anyscale.job.list() share one client, so set ANYSCALE_EXTRA_HEADERS before the first call.
  • Requests to other hosts never carry these headers, including a redirect away from the Anyscale API, cloud storage uploads and downloads, cluster connections and the PyPI version check.
  • The hidden anyscale session commands and the web terminal's command log send their API calls after the credential check with plain requests. These calls do not carry the custom headers.
  • Header values are never printed or sent in usage telemetry; with ANYSCALE_DEBUG=1 the CLI prints only their names. Prefer the environment variable for secrets, because command-line arguments end up in shell history and process listings.

After making any changes to the CLI, be sure to run pip install -U -e . from within the frontend/cli directory to update your environment with the latest modifications.

Metadata

Release files for anyscale 0.26.119

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

Source distribution (sdist)

Source distribution for anyscale 0.26.119
File Size Uploaded Provenance Actions
anyscale-0.26.119.tar.gz 2.3 MB Without provenance Details for anyscale-0.26.119.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for anyscale 0.26.119
File Interpreter ABI Platform Actions
anyscale-0.26.119-py3-none-any.whl Python 3 none any Details for anyscale-0.26.119-py3-none-any.whl

Total release size: 6.6 MB

Release files / anyscale-0.26.119.tar.gz

Download URL anyscale-0.26.119.tar.gz
Size 2.3 MB
Tags Source
SHA-256 checksum
How to use checksums
a2cdf9af7ba3eddb9db2f0cb0220079dfb67a1b43b7bbf795083a855c30407b8
BLAKE2b-256 checksum
How to use checksums
e88f87a65d699d0dbb0ffe201c12c941615c74166e6ce3a0ebf305e02855835d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Release files / anyscale-0.26.119-py3-none-any.whl

Download URL anyscale-0.26.119-py3-none-any.whl
Size 4.2 MB
Tags Python 3
SHA-256 checksum
How to use checksums
a5a468cb88db9df3edccd30bd530b75d64f4c1c50411fb3fa5d312c5a9045f39
BLAKE2b-256 checksum
How to use checksums
246089aac7e263fe15e41fa9501145d504c034ddc9a8ff3cc91fc7604e20cd40
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Security for anyscale 0.26.119

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

0.26.119 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