# dunebox-avd-build-cfg

### Arguments

<table><thead><tr><th width="175">Argument</th><th width="99" align="center">Type</th><th width="99" align="center">Optional</th><th width="373">Interpretation</th></tr></thead><tbody><tr><td><code>--server</code></td><td align="center"><code>String</code></td><td align="center">Yes</td><td>URL of Dunebox server. Overrides the configured value if provided. </td></tr><tr><td><code>--access-key</code></td><td align="center"><code>String</code></td><td align="center">Yes</td><td>Your access key. Overrides configured value if provided. </td></tr><tr><td><code>--secret-key</code></td><td align="center"><code>String</code></td><td align="center">Yes</td><td>Your secret key. Overrides configured value if provided.</td></tr><tr><td><code>--pretty</code></td><td align="center"><code>flag</code></td><td align="center">Yes</td><td>Pretty print output</td></tr></tbody></table>

### Successful Output

When called without the `--pretty` flag, the result is a JSON object with the following fields

<table><thead><tr><th width="165" align="center">Field</th><th width="212" align="center">Type</th><th>Interpretation</th></tr></thead><tbody><tr><td align="center"><code>device_defn</code></td><td align="center"><code>Array&#x3C;DeviceDefn></code></td><td>Available device definitions, which are virtual abstractions of the real devices, like the Google Pixel 5</td></tr><tr><td align="center"><code>avd_base</code></td><td align="center"><code>Array&#x3C;AvdBase></code></td><td>Available AVD base images</td></tr></tbody></table>

Each `DeviceDefn` has the following fields:&#x20;

<table><thead><tr><th width="149" align="center">Field</th><th width="186" align="center">Type</th><th>Interpretation</th></tr></thead><tbody><tr><td align="center"><code>id</code></td><td align="center"><code>String</code></td><td>UID of the device definition</td></tr><tr><td align="center"><code>name</code></td><td align="center"><code>String</code></td><td>Name of the Device</td></tr><tr><td align="center"><code>oem</code></td><td align="center"><code>String</code></td><td>OEM of the Device</td></tr></tbody></table>

Each `AvdBase` has the following fields:&#x20;

<table><thead><tr><th width="149" align="center">Field</th><th width="186" align="center">Type</th><th>Interpretation</th></tr></thead><tbody><tr><td align="center"><code>api</code></td><td align="center"><code>uint8</code></td><td>API level of the AVD</td></tr><tr><td align="center"><code>tag</code></td><td align="center"><code>String</code></td><td>Tag of the base image (e.g. <code>google_apis)</code></td></tr><tr><td align="center"><code>abi</code></td><td align="center"><code>String</code></td><td>Application Binary Interface of the AVD (e.g. <code>x86_64</code>)</td></tr></tbody></table>

The result is pretty printed when called with the `--pretty` flag.&#x20;

<div><figure><img src="/files/mPjnjpQFGSVmwzDKw5Df" alt=""><figcaption></figcaption></figure> <figure><img src="/files/LOE6EObyFnAzqsooL5Y1" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://oda.moreficent.com/command-reference/dunebox-avd-build-cfg.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
