gplay auth login
Register a Google Cloud service account JSON as a named Account in the local gplay registry and mark it active so subsequent commands use it without an explicit --account flag.
The credential is stored in the OS keystore (macOS Keychain, Windows
Credential Manager, or Linux Secret Service). On systems without a keystore
daemon (headless Linux, CI containers), gplay transparently falls back to a
0600 file under the config directory. The active backend is reported by
gplay auth status and logged once per process at -v.
Pass --activate=false to add a second Account without changing which one is active. (The very first registered Account becomes active regardless, so the registry is never left without one when --activate=false is set.)
gplay auth login [flags]| Flag | Description |
|---|---|
--activate | mark the new Account active (default true) (default true) |
--developer-id gplay team | Play Console Developer account id to record on this Account (for gplay team) |
--name string | friendly Account name (default: derived from client_email) |
Global flags
Section titled “Global flags”| Flag | Description |
|---|---|
--account string | name of a stored Account to use (overrides env and active Account) |
--retry int | retry transient failures (transport errors, 5xx, 429) up to N times with exponential backoff (default: 0, no retry) |
--service-account string | path to a service-account JSON, or inline JSON content (overrides --account, env, and active Account) |
--timeout duration | per-request API timeout, e.g. 30s or 2m (default: 60s for control-plane calls, none for uploads) |
-v, --verbose | log flow steps to stderr (info level) |