Struct DataSpec 

pub struct DataSpec<'a> {
    pub path: Option<&'a str>,
    pub source: Option<&'a str>,
    pub ssh: Option<&'a SshConfig>,
}

The data half of the join recipe, as resolved from flags over the join: block.

Fields

path: Option<&'a str>

Local source root (the mountpoint, when source is set).

source: Option<&'a str>

<scheme>://<target> transport that establishes path.

ssh: Option<&'a SshConfig>

The join block’s tunnel credentials. Reused for the data mount: in the shape this exists for, the data host IS the controller box the tunnel already authenticates against, so a second key field would be surface that only ever repeats the first one.

One consequence belongs in the operator’s hands rather than in their debugging: a forced command= on that key covers subsystem requests, so a join key guardrailed with /usr/sbin/nologin turns sftp away and the mount never comes up while the tunnel keeps working (ssh -N requests no command at all). Either the key permits sftp (internal-sftp -R), or the source root is mounted during provisioning and path is declared bare — which is also the answer for a box whose mount needs different credentials entirely. Both spellings are in the guardrail recipe in docs/ddp/02-cluster-guide.md.

Trait Implementations

impl<'a> Debug for DataSpec<'a>

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

Formats the value using the given formatter.

impl<'a> Default for DataSpec<'a>

fn default() -> DataSpec<'a>

Returns the “default value” for a type.