Authenticate Vespa CLI with Vespa Cloud control plane. This is preferred over api-key for interactive use
Authenticate Vespa CLI with Vespa Cloud control plane. This is preferred over api-key for interactive use.
This command runs a browser-based authentication flow for the Vespa Cloud control plane.
Use –file-storage flag to store the refresh token in unencrypted files instead of the system keyring. This is useful in SSH/CI/Docker environments where keyring access may not be available.
Use –no-browser to print the login URL to standard output instead of opening a browser automatically. This is useful in non-interactive terminals (e.g. Git Bash on Windows) or remote sessions where a browser cannot be opened.
Use –batch to suppress all human-readable output and print only machine-readable key=value pairs:
code=
vespa auth login [flags]
$ vespa auth login
--batch Print machine-readable key=value pairs (code, url) and suppress all other output
--file-storage Use file storage (unencrypted) instead of keyring for storing refresh token
-h, --help help for login
--no-browser Print login URL to standard output without confirmation and without automatic opening of browser
-a, --application string The application to use. Format "tenant.application.instance" - instance is optional (tenant required for cloud targets)
-C, --cluster string The container cluster to use. This is only required for applications with multiple clusters
-c, --color string Whether to use colors in output. Must be "auto", "never", or "always" (default "auto")
-i, --instance string The instance of the application to use
-q, --quiet Print only errors
-t, --target string The target platform to use. Must be "local", "cloud", "hosted" or an URL (default "local")
-z, --zone string The zone to use. This defaults to a dev zone (cloud only)