> 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/tasks.md).

# Jira Tickets

Generated from `jira_links` on `2026-05-12`.

## Status

| Key      | Title                                                                        | Status |
| -------- | ---------------------------------------------------------------------------- | ------ |
| SDK-1929 | \[Terraform] Change 'WaitUntilAvailable' behavior for DBaaS cluster creation | DONE   |
| SDK-2528 | \[Terraform] Modify test.yml workflow                                        | DONE   |

> **Status column instructions:** When Claude works on a ticket, it fills this column with `DONE` if the task was completed, or `BLOCKED` if it could not be finished (append a brief reason in parentheses, e.g. `BLOCKED (missing API access)`). Leave blank until worked on.

***

## SDK-1929 — \[Terraform] Change 'WaitUntilAvailable' behavior for DBaaS cluster creation

**Link:** <https://hosting-jira.1and1.org/browse/SDK-1929>

**Description:**

Change ***WaitUntilAvailable*** behavior for DBaaS cluster creation.

When creating a DBaaS cluster, the cluster can enter the ***FAILED*** state. After entering this state, there is no point in waiting for the cluster to become ***AVAILABLE*** since this will never happen, so we need to change the ***Wait*** mechanism.

**Attachments:**

*(none)*

***

## SDK-2528 — \[Terraform] Modify test.yml workflow

**Link:** <https://hosting-jira.1and1.org/browse/SDK-2528>

**Description:**

From **test.yml**:

```yaml
 name: Run tests for ${{ github.event.inputs.test-tags }}
  if: ${{ github.event.inputs.test-tags != '' && github.events.inputs.failfast == true }}
  run: go test ./... -v -failfast -timeout 240m -tags ${{ github.event.inputs.test-tags }}
- name: Run tests for ${{ github.event.inputs.test-tags }} no failfast
  if: ${{ github.event.inputs.test-tags != '' && github.events.inputs.failfast == false }}
  run: go test ./... -v -timeout 6h -tags ${{ github.event.inputs.test-tags }}
- name: Run tests without tags
  if: ${{ github.event.inputs.test-tags == ''}}
  run: go test ./... -v -failfast -timeout 180m
```

Timeout value differs when using the **failfast** option. When setting the **failfast** option, I don't expect a change in the timeout value. The timeout value should be the same for both scenarios but it would be nice to be able to specify the timeout value as an input parameter.

**Attachments:**

*(none)*


---

# 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/tasks.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.