deps: Bump terragrunt version to 0.89.0

[elastic-observability-automation]

deps: Bump terragrunt version

deps(terragrunt): Bump terragrunt version to 0.89.0

1 file(s) updated with "0.89.0\n": * tests/terragrunt/version/.terragrunt-version

0.89.0

Release published on the 2025-10-06 15:05:52 +0000 UTC at the url https://github.com/gruntwork-io/terragrunt/releases/tag/v0.89.0

Several experimental features have been made generally available.

## 🛠️ Breaking Changes

### Runner-pool

Terragrunt now supports the Runner Pool concurrency model, replacing the traditional group-based concurrency model with a dynamic scheduler by default.

Instead of waiting for groups of units that block downstream units to complete their runs, the Runner Pool executes each unit as soon as its dependencies (or dependents for destroys) are resolved. This improves efficiency, reduces bottlenecks, and limits the impact of individual failures on the run of the entire queue.

### ✨New Features

- Dynamically schedules Units as soon as dependencies (or dependents) are satisfied
- Improves throughput for large stacks
- Provides better fault-isolation for failed units

<p align="center">

<img width="789" height="480" alt="image" src="https://github.com/user-attachments/assets/7d88e437-2d5f-4477-86eb-0733b7062f0d" />

</p>

### Report

The experimental Report feature is now stable and enabled by default.

Every Terragrunt run will now emit a short summary at the end of the run that looks like the following by default:

```bash
$ terragrunt run --all plan

# Omitted for brevity...

❯❯ Run Summary  3 units  62ms
   ────────────────────────────
   Succeeded    3

```

This summary will give a high-level overview of the run results for units in a given Terragrunt run.

You can optionally request a CSV or JSON report of runs as well, giving you detailed insights as to the performance of each run using the `--report` flag:

```bash
terragrunt run --all plan --report-schema-file report.schema.csv
```

```csv
Name,Started,Ended,Result,Reason,Cause
first-exclude,2025-06-05T16:28:41-04:00,2025-06-05T16:28:41-04:00,excluded,exclude block,
second-exclude,2025-06-05T16:28:41-04:00,2025-06-05T16:28:41-04:00,excluded,exclude block,
first-failure,2025-06-05T16:28:41-04:00,2025-06-05T16:28:42-04:00,failed,run error,
first-success,2025-06-05T16:28:41-04:00,2025-06-05T16:28:41-04:00,succeeded,,
second-failure,2025-06-05T16:28:41-04:00,2025-06-05T16:28:42-04:00,failed,run error,
second-success,2025-06-05T16:28:41-04:00,2025-06-05T16:28:41-04:00,succeeded,,
second-early-exit,2025-06-05T16:28:42-04:00,2025-06-05T16:28:42-04:00,early exit,run error,
first-early-exit,2025-06-05T16:28:42-04:00,2025-06-05T16:28:42-04:00,early exit,run error,
```

```bash
terragrunt run --all plan --report-schema-file report.schema.json
```

```json
[
  {
    "Name": "first-exclude",
    "Started": "2025-06-05T16:28:41-04:00",
    "Ended": "2025-06-05T16:28:41-04:00",
    "Result": "excluded",
    "Reason": "exclude block"
  },
  {
    "Name": "first-success",
    "Started": "2025-06-05T16:28:41-04:00",
    "Ended": "2025-06-05T16:28:41-04:00",
    "Result": "succeeded"
  }
]

```

### ✨New Features

- Generates detailed run reports (CSV and JSON formats supported)
- Displays run summaries directly in the CLI output
- Allows disabling summaries if desired

To learn more about the Run Report feature, read the dedicated guide on Run Reports [here](https://terragrunt.gruntwork.io/docs/features/run-report/).

### 🔧 Migration Guide

No action is required

To disable summary output explicitly, use `--disable-report-summary`:

```bash
terragrunt run --all plan --disable-report-summary
```

### Auto OpenTofu Provider Cache Directory

Terragrunt now automatically configures OpenTofu’s **native provider caching mechanism** by default when running with OpenTofu > = 1.10.

Note that if you are using Terraform, you will not be able to take advantage of this new feature.

This feature is only possible in OpenTofu due to the hard work and coordination with the OpenTofu team to ensure that concurrent access to the provider cache directory is safe for all OpenTofu users, regardless of whether they use Terragrunt.

<p align="center">
<img width="912" height="486" alt="Screenshot 2025-06-25 at 12 38 05 PM" src="https://github.com/user-attachments/assets/214cff8d-4fbb-4e70-aa96-c026e91038d7" />
</p>


### ✨New Features

- Automatically sets the `TF_PLUGIN_CACHE_DIR` environment variable
- Uses OpenTofu’s native provider cache instead of Terragrunt’s internal cache server
- Provides improved concurrency safety in multi-runner and CI environments

### 🔧 Migration Guide

No action is required if you’re running OpenTofu > = 1.10 — provider caching will be configured automatically.

To disable this behavior, use the `--no-auto-provider-cache-dir` flag:

```bash
terragrunt run --all apply --no-auto-provider-cache-dir
```

## What's Changed
* chore: Marked as completed runner-pool, reports and provider cache by @denis256 in https://github.com/gruntwork-io/terragrunt/pull/4900
* fix: Properly sets discovery context so that `plan -destroy` and `apply -destroy` work right by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/4887
* docs: Implement view plans button by @karlcarstensen in https://github.com/gruntwork-io/terragrunt/pull/4890
* docs: Visual updates to form by @karlcarstensen in https://github.com/gruntwork-io/terragrunt/pull/4902
* docs: Fix docs flag name by @rubensf in https://github.com/gruntwork-io/terragrunt/pull/4908


**Full Changelog**: https://github.com/gruntwork-io/terragrunt/compare/v0.88.1...v0.89.0

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!