> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/tools-terraform/docs/data-sources/mariadb_versions_v2.md).

# ionoscloud\_mariadb\_versions\_v2

Lists supported IONOS CLOUD MariaDB V2 Versions.

The `ionoscloud_mariadb_versions_v2` data source can be used to retrieve the supported MariaDB V2 versions in a given location.

## Example Usage

```hcl
data "ionoscloud_mariadb_versions_v2" "example" {
  location = "de/txl"
}
```

## Argument Reference

* `location` - (Required)\[string] The location to query. Available locations: `de/fra`, `de/fra/1`, `de/fra/2`, `de/txl`, `es/vit`, `fr/par`, `gb/bhx`, `gb/lhr`, `us/ewr`, `us/las`, `us/mci`.

## Attributes Reference

The following attributes are returned by the datasource:

* `items` - List of supported versions. Each item includes:
  * `id` - The ID (UUID) of the version.
  * `version` - The MariaDB version string (e.g. `11.4`).
  * `status` - The support status of the version.
  * `comment` - Additional human-readable information about the version lifecycle.
  * `can_upgrade_to` - List of versions that a cluster running this version can be upgraded to.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/tools-terraform/docs/data-sources/mariadb_versions_v2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.