> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mirurobotics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Validate

Validate local config files satisfy a release's schemas.

### API key scopes

If validating from a [CI pipeline](/developers/ci/overview), the following API key scopes are required:

* `releases:read`
* `config_schemas:read`

### Usage

<Tabs>
  <Tab title="Current directory">
    By default, validating a deployment reads the config files from the current directory.

    ```bash theme={null}
    miru deployment validate \
      --release {release-version}
    ```
  </Tab>

  <Tab title="Custom root">
    Use the `--root` flag to read the config files from a custom root directory.

    ```bash theme={null}
    miru deployment validate \
      --release {release-version} \
      --root {root-dir}
    ```
  </Tab>

  <Tab title="Device paths">
    Use `--root /` to read config files from the exact location they are written to on production devices.

    ```bash theme={null}
    miru deployment validate \
      --release {release-version} \
      --root /
    ```
  </Tab>
</Tabs>

<Tip>
  Use `sudo miru ...` to read config files from restricted paths.
</Tip>

**Flags**

<ParamField path="--release" type="string" required>
  Release version to validate against, matched exactly.

  Examples: `v1.2.0`
</ParamField>

<ParamField path="--root" type="string">
  Directory to read config files from. Defaults to the current directory.

  Each slot is read from its device path relative to this directory, so `/srv/miru/configs/mobility.json` is read from `{--root}/srv/miru/configs/mobility.json`. Pass `/` to read files at their actual device paths.

  Examples: `./robot-42-fs`, `/`
</ParamField>

### Examples

```bash theme={null}
$ miru deployment validate \
    --release v1.2.0 \
    --root ./robot-42-fs

◐ Validating release v1.2.0

  /home/you/robot-42-fs
  └── srv/miru/configs
      ├── mobility.json  Mobility
      └── planning.json  Planning

✓ Deployment Valid
```
