Struct DriveAccountSettings 

pub struct DriveAccountSettings {
    pub client_id: Option<String>,
    pub client_secret: Option<String>,
    pub refresh_token: Option<String>,
    pub scope: Option<String>,
    pub email_address: Option<String>,
    pub chrome_profile_from_email: bool,
    pub browser_command: Option<String>,
}

A single named Google Drive account’s stored OAuth2 credentials, inside the drive.accounts map (issue #1520, ADR-0069).

A field-for-field mirror of GmailAccountSettings: a Drive account and a Gmail account are different credential axes even when the underlying human is the same person, so the two blocks compose independently rather than one nesting under the other. See email_address’s own doc comment below for how it’s populated and used — never for authentication itself.

Fields

client_id: Option<String>

OAuth2 client id from the account’s Google Cloud project.

client_secret: Option<String>

OAuth2 client secret from the account’s Google Cloud project.

refresh_token: Option<String>

The long-lived refresh token obtained by drive auth login (issue #1523).

scope: Option<String>

The OAuth2 scope this account was authorized with, as the raw string Google granted. Stays a plain String here (unlike Gmail’s equivalent settings field, for the same reason): this is a status-reporting cache of whatever was actually granted, not the value driving a live login decision — that’s crate::drive::auth::DriveScope, read from this field via crate::drive::auth::DriveScope::from_granted (ADR-0070, reversing ADR-0069 §2’s “no DriveScope enum, read-only by design”).

email_address: Option<String>

Google account address for this account. Populated opportunistically by drive auth status when absent, but may also be set by hand ahead of the first login — e.g. to opt into chrome_profile_from_email below. An explicit value is never overwritten by the backfill. Never used for authentication itself, only for browser targeting.

chrome_profile_from_email: bool

Opt-in (default false): resolve which local Chrome profile is signed into email_address and launch drive auth login’s authorization URL targeting that profile, instead of the OS default browser. Resolution failure (Chrome not installed, zero or multiple matching profiles, …) always falls back to the default browser — never a hard login failure. Ignored when browser_command is set. (Inherited from Gmail by field — ADR-0067 via ADR-0069.)

browser_command: Option<String>

Explicit browser launch command for drive auth login, {url} templated (or appended if no placeholder is present) — the manual escape hatch, e.g. to target a specific Chrome profile by hand or a non-Chrome browser entirely. Mirrors SNOWFLAKE_BROWSER_COMMAND (crate::snowflake). Takes precedence over chrome_profile_from_email. (Inherited from Gmail by field — ADR-0067.)

Trait Implementations

impl Debug for DriveAccountSettings

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for DriveAccountSettings

fn default() -> DriveAccountSettings

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for DriveAccountSettings

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.