> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/dataos-resources/bundle/field-reference.md).

# Field reference

Use this page to look up Bundle manifest fields, required values, and nested options.

## Top-level fields

| Field         | Description                               | Required |
| ------------- | ----------------------------------------- | -------- |
| `version`     | Manifest version. Use `v2alpha`.          | Yes      |
| `name`        | Bundle Resource name.                     | Yes      |
| `type`        | Resource type. Use `bundle`.              | Yes      |
| `description` | Human-readable description of the Bundle. | No       |
| `tags`        | Labels for grouping and discovery.        | No       |
| `bundle`      | Bundle-specific configuration.            | Yes      |

## `bundle` fields

| Field                 | Description                                               | Required |
| --------------------- | --------------------------------------------------------- | -------- |
| `bundle.resources`    | List of Resources included in the Bundle.                 | Yes      |
| `bundle.schedule`     | Optional create/delete schedule for the Bundle.           | No       |
| `bundle.workspaces`   | Optional workspace definitions used by bundled Resources. | No       |
| `bundle.properties`   | Additional key-value metadata for the Bundle.             | No       |
| `bundle.manageAsUser` | User context used to manage the Bundle.                   | No       |

## `bundle.resources[]` fields

| Field                                     | Description                                                                  | Required |
| ----------------------------------------- | ---------------------------------------------------------------------------- | -------- |
| `bundle.resources[].id`                   | Unique ID for the Resource inside the Bundle DAG.                            | Yes      |
| `bundle.resources[].file`                 | Path to a Resource manifest file.                                            | No       |
| `bundle.resources[].spec`                 | Inline Resource manifest.                                                    | No       |
| `bundle.resources[].workspace`            | Workspace where a workspace-level Resource should be created.                | No       |
| `bundle.resources[].dependencies`         | Resource IDs that must be processed before this Resource.                    | No       |
| `bundle.resources[].dependencyConditions` | Conditions that dependencies must satisfy before this Resource is processed. | No       |

## `bundle.resources[].dependencyConditions[]` fields

| Field                                                        | Description                                 | Required                                 |
| ------------------------------------------------------------ | ------------------------------------------- | ---------------------------------------- |
| `bundle.resources[].dependencyConditions[].resourceId`       | ID of the dependent Resource being checked. | Yes, when `dependencyConditions` is used |
| `bundle.resources[].dependencyConditions[].status.is`        | Accepted exact status values.               | No                                       |
| `bundle.resources[].dependencyConditions[].status.contains`  | Accepted status fragments.                  | No                                       |
| `bundle.resources[].dependencyConditions[].runtime.is`       | Accepted exact runtime values.              | No                                       |
| `bundle.resources[].dependencyConditions[].runtime.contains` | Accepted runtime fragments.                 | No                                       |

## Notes

* Use either `file` or `spec` for each resource entry.
* Use `dependencies` to build the deployment order.
* Use `dependencyConditions` when status alone is not enough.

For behavior and design guidance, see [Core concepts](/references/dataos-resources/bundle/core-concepts.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/references/dataos-resources/bundle/field-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.