Configuration Fetch and Drift Hashes#

rauto config fetch retrieves complete device configurations with the command catalog defined for each Profile. It is intended for backups, drift detection, and configuration review rather than individual operational queries.

#Fetch one device

rauto config fetch --connection core-sw-01
rauto config fetch --connection core-sw-01 --kind startup

The default kind is running. A Profile can expose running, startup, or another locally defined kind. Use rauto config command to inspect or override the command mapping for custom environments.

#Fetch many devices

config fetch uses the same selectors as multi-target exec, flow, and show:

rauto config fetch \
  --target core-sw-01 \
  --group access \
  --label campus \
  --max-parallel 8 \
  --output-dir ./config-archive

Repeat --target, --group, or --label/--tag as needed. The selectors form a deduplicated union. rauto resolves and validates every target before starting connections, then limits active sessions with --max-parallel.

Use --output <file> for one target and --output-dir <directory> for multi-target archives.

#Raw and normalized hashes

Each successful result includes:

• the exact raw configuration and its SHA-256 hash
• normalized content with volatile lines removed
• a SHA-256 hash of that normalized content
• the resolved Profile, configuration kind, command, and fetch time

Normalized hashes make drift comparisons stable when devices include timestamps, generated identifiers, or other frequently changing lines. Print or save normalized content with:

rauto config fetch --connection core-sw-01 --normalized

Bundled volatile-line rules can be extended per Profile with rauto config volatile. Custom command and normalization records override the bundled catalog without changing release assets.

#Session retries

For read-only fetches over unstable links, retries can be enabled explicitly:

rauto config fetch --group branch \
  --session-retries 2 \
  --retry-initial-backoff-ms 300 \
  --retry-max-backoff-ms 2000

Retries use capped exponential backoff and are disabled by default. They have at-least-once semantics, so only enable them for repeat-safe operations. Authentication failures remain excluded unless --retry-authentication-errors is set.

#Web workspace

The Web Config Fetch workspace supports current-device and batch targets, configuration kind selection, normalized content, retry overrides, raw and normalized hashes, and direct downloads.