fix(gen): add opentofu as terraform alternative

Author: bene2k1

faq/iam.mdx

@@ -27,7 +27,7 @@ IAM enables you to manage access control to all Scaleway products.
 You may decide yourself whether to leave these automatically-created IAM applications and policies in place, [edit the policies](/iam/how-to/manage-policies/) to change permissions as required, or [generate new API keys for individual users](/iam/how-to/create-api-keys/) to define rights per-user via the creation of [new policies](/iam/how-to/create-policy/) for those users.
 
 ## What are applications, and why do I need them?
-Applications represent the identity of non-human users (such as a CI pipeline, a custom script, or a Terraform provider). They are used to attach permissions and API keys to these operations - without being linked to specific users and their own rights.
+Applications represent the identity of non-human users (such as a CI pipeline, a custom script, or a Terraform/OpenTofu/OpenTofu provider). They are used to attach permissions and API keys to these operations - without being linked to specific users and their own rights.
 
 ## Why do I have to select a preferred Project for Object Storage when I create an API key?
 Due to limitations on the Object Storage API, API keys cannot perform Object Storage actions on several projects at the same time. Whenever you generate an API key that will be used on Object Storage, you must specify a preferred project where the API key will be able to perform actions. For more information, refer to the [Using IAM API keys with Object Storage](/iam/api-cli/using-api-key-object-storage/) documentation page.

faq/messaging-and-queuing.mdx

@@ -31,9 +31,9 @@ The following subscriber types are supported:
 
 For more details on supported and unsupported Topics and Events features, see our [dedicated page](/messaging/reference-content/sns-support/).
 
-## Can I configure Scaleway NATS via Terraform?
+## Can I configure Scaleway NATS via Terraform/OpenTofu/OpenTofu?
 
-Yes, check out our [tutorial](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/guides/mnq_with_nats_terraform_provider) on how to configure Scaleway NATS with the Terraform [NATS Jetstream provider](https://registry.terraform.io/providers/nats-io/jetstream/latest/docs).
+Yes, check out our [tutorial](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/guides/mnq_with_nats_terraform_provider) on how to configure Scaleway NATS with the Terraform/OpenTofu/OpenTofu [NATS Jetstream provider](https://registry.terraform.io/providers/nats-io/jetstream/latest/docs).
 
 ## How are NATS, Queues, and Topics and Events billed?
 

macros/developer-tools/scaleway-environment-variables.mdx

@@ -8,15 +8,15 @@ The following standardized Scaleway environment variables are used for the CLI a
 
 | Variable                       | Description                                                                                      | Legacy variables                                                                                              |
 | :----------------------------- | :----------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------ |
-| `$SCW_ACCESS_KEY`              | The [access key](/iam/how-to/create-api-keys/) of a token    | `$SCALEWAY_ACCESS_KEY` (used by Terraform)                                                                 |
-| `$SCW_SECRET_KEY`              | The [secret key](/iam/how-to/create-api-keys/) of a token   | `$SCW_TOKEN` (used by the CLI), `$SCALEWAY_TOKEN` (used by Terraform), `$SCALEWAY_ACCESS_KEY` (used by Terraform) |                                                                                                         |
-| `$SCW_DEFAULT_REGION`          | Your default [region](https://www.scaleway.com/en/developers/api/#regions-and-zones)             | `$SCW_REGION` (used by the CLI),`$SCALEWAY_REGION` (used by Terraform)                                        |
-| `$SCW_DEFAULT_ZONE`            | Your default [Availability Zone](https://www.scaleway.com/en/developers/api/#regions-and-zones)  | `$SCW_ZONE` (used by the CLI),`$SCALEWAY_ZONE` (used by Terraform)                                            |
+| `$SCW_ACCESS_KEY`              | The [access key](/iam/how-to/create-api-keys/) of a token    | `$SCALEWAY_ACCESS_KEY` (used by Terraform/OpenTofu/OpenTofu/OpenTofu)                                                                 |
+| `$SCW_SECRET_KEY`              | The [secret key](/iam/how-to/create-api-keys/) of a token   | `$SCW_TOKEN` (used by the CLI), `$SCALEWAY_TOKEN` (used by Terraform/OpenTofu/OpenTofu/OpenTofu), `$SCALEWAY_ACCESS_KEY` (used by Terraform/OpenTofu/OpenTofu) |                                                                                                         |
+| `$SCW_DEFAULT_REGION`          | Your default [region](https://www.scaleway.com/en/developers/api/#regions-and-zones)             | `$SCW_REGION` (used by the CLI),`$SCALEWAY_REGION` (used by Terraform/OpenTofu)                                        |
+| `$SCW_DEFAULT_ZONE`            | Your default [Availability Zone](https://www.scaleway.com/en/developers/api/#regions-and-zones)  | `$SCW_ZONE` (used by the CLI),`$SCALEWAY_ZONE` (used by Terraform/OpenTofu)                                            |
 | `$SCW_API_URL`                 | URL of the API                                                                                   | -                                                                                                             |
 | `$SCW_INSECURE`                | Set this variable to `true` to enable the [insecure mode](/iot-hub/concepts/#insecure-connection)                                           | `$SCW_TLSVERIFY` (inverse flag used by the CLI)                                                               |
 | `$SCW_PROFILE`                 | Set the configuration profile to use                                                             | -                                                                                                             |
 | `$SCW_PROJECT_ID`              | Your [Project ID](https://console.scaleway.com/project/settings) | `$SCW_DEFAULT_PROJECT_ID`                                                                                     |
-| `$SCW_ORGANIZATION_ID`         | Your [Organization ID](https://console.scaleway.com/organization/settings) | `$SCW_DEFAULT_ORGANIZATION_ID`, `$SCW_ORGANIZATION` (used by the CLI),`$SCALEWAY_ORGANIZATION` (used by Terraform) |
+| `$SCW_ORGANIZATION_ID`         | Your [Organization ID](https://console.scaleway.com/organization/settings) | `$SCW_DEFAULT_ORGANIZATION_ID`, `$SCW_ORGANIZATION` (used by the CLI),`$SCALEWAY_ORGANIZATION` (used by Terraform/OpenTofu) |
 
 ## Environment variables priority
 
@@ -26,6 +26,6 @@ The order of precedence, from highest to lowest is the following.
 
 1. Environment variables defined in your command-line environment.
 
-2. Static variables (i.e. variables set in a Terraform configuration file).
+2. Static variables (i.e. variables set in a Terraform/OpenTofu configuration file).
 
 3. Variables defined in the [Scaleway configuration file](/scaleway-sdk/reference-content/scaleway-configuration-file/) 

pages/cockpit/how-to/send-logs-from-k8s-to-cockpit.mdx

@@ -13,7 +13,7 @@ dates:
   posted: 2025-01-20
 ---
 
-In this page, we will show you how to send application logs from your Kubernetes cluster to your Cockpit using either a Helm chart or deploying a Helm chart with [Terraform](https://www.terraform.io/).
+In this page, we will show you how to send application logs from your Kubernetes cluster to your Cockpit using either a Helm chart or deploying a Helm chart with [Terraform](https://www.terraform.io/) or [OpenTofu](https://opentofu.org/).
 
 We will use the [k8s-monitoring](https://artifacthub.io/packages/helm/grafana/k8s-monitoring/1.6.16) Helm Chart, which installs an Alloy Daemon set to export your Kubernetes cluster's logs to your Cockpit.
 
@@ -100,11 +100,11 @@ Once you have configured your `values.yml` file, you can use Helm to deploy the
       helm list
       ```
 
-## Send Kubernetes logs using Helm chart with Terraform
+## Send Kubernetes logs using Helm chart with Terraform/OpenTofu
 
-You can also use Terraform to manage and deploy Helm charts, providing you with more automation and consistency to manage your Kubernetes resources.
+You can also use Terraform/OpenTofu to manage and deploy Helm charts, providing you with more automation and consistency to manage your Kubernetes resources.
 
-1. Create a `provider.tf` file and paste the following template to set up the Helm Terraform provider:
+1. Create a `provider.tf` file and paste the following template to set up the Helm Terraform/OpenTofu provider:
     ```terraform
     provider "helm" {
       kubernetes {
@@ -130,7 +130,7 @@ You can also use Terraform to manage and deploy Helm charts, providing you with
     }
     ```
 3. Save your changes.
-4. Run `terraform init` to initialize your Terraform configuration and download any necessary providers.
+4. Run `terraform init` to initialize your Terraform/OpenTofu configuration and download any necessary providers.
 5. Run `terraform apply` to apply your configuration.
 6. Type `yes` when prompted to confirm the actions.
 

pages/cockpit/how-to/send-metrics-from-k8s-to-cockpit.mdx

@@ -14,7 +14,7 @@ dates:
 ---
 
 
-In this page we will show you how to send application metrics from your Kubernetes cluster to your Cockpit, either by using a Helm chart or deploying a Helm chart with [Terraform](https://www.terraform.io/).
+In this page we will show you how to send application metrics from your Kubernetes cluster to your Cockpit, either by using a Helm chart or deploying a Helm chart with [Terraform](https://www.terraform.io/) or [OpenTofu](https://opentofu.org/).
 
 We will use the [k8s-monitoring](https://artifacthub.io/packages/helm/grafana/k8s-monitoring/1.6.16) Helm Chart, which installs an Alloy Daemon set to export your Kubernetes cluster's metrics to your Cockpit.
 
@@ -88,7 +88,7 @@ spec:
   ...
 ```
 
-### Terraform deployment template
+### Terraform/OpenTofu deployment template
 
 ```terraform
 resource "kubernetes_deployment_v1" "your_application_deployment" {
@@ -109,9 +109,9 @@ resource "kubernetes_deployment_v1" "your_application_deployment" {
 }
 ```
 
-## Send Kubernetes metrics using Helm chart with Terraform
+## Send Kubernetes metrics using Helm chart with Terraform/OpenTofu
 
-1. Create a `provider.tf` file and paste the following template to set up the Helm Terraform provider:
+1. Create a `provider.tf` file and paste the following template to set up the Helm Terraform/OpenTofu provider:
     ```terraform
     provider "helm" {
       kubernetes {
@@ -137,7 +137,7 @@ resource "kubernetes_deployment_v1" "your_application_deployment" {
     }
     ```
 3. Save your changes.
-4. Run `terraform init` to initialize your Terraform configuration and download any necessary providers.
+4. Run `terraform init` to initialize your Terraform/OpenTofu configuration and download any necessary providers.
 5. Run `terraform apply` to apply your configuration.
 6. Type `yes` when prompted to confirm the actions.
 

pages/cockpit/index.mdx

@@ -52,7 +52,7 @@ meta:
 <Grid>
 
     <DefaultCard
-        title="Using Cockpit with Terraform"
+        title="Using Cockpit with Terraform/OpenTofu"
         url="/tutorials/use-cockpit-with-terraform/"
         label="Read more"
     />

pages/elastic-metal/api-cli/elastic-metal-with-api.mdx

@@ -16,7 +16,7 @@ categories:
 
 Scaleway's [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/) provide 100% dedicated resources while offering the flexibility and scalability of the cloud, including hourly billing and full customization. The hardware is entirely dedicated to you — free from virtualization, overallocation, or neighboring tenants.
 
-Elastic Metal servers also feature a robust [REST API](https://www.scaleway.com/en/developers/api/elastic-metal/) that enables seamless automation of tasks and deployments. Integration with tools like [Terraform](https://www.terraform.io/) further streamlines infrastructure management.
+Elastic Metal servers also feature a robust [REST API](https://www.scaleway.com/en/developers/api/elastic-metal/) that enables seamless automation of tasks and deployments. Integration with tools like [Terraform](https://www.terraform.io/) or [OpenTofu](https://opentofu.org/) further streamlines infrastructure management.
 
 The **one-command deployment feature** accelerates server provisioning by combining delivery and setup into a single API call. This simplifies server provisioning, ensuring your machine is fully operational in less than 15 minutes.
 

pages/gpu/how-to/use-scratch-storage-h100-instances.mdx

@@ -52,7 +52,7 @@ You need to add an extra volume, for example:
     "volumes":{"1":{"name":"scratch-volume","volume_type":"scratch","size":3000000000000}}
     ```
 
-## How can I add scratch storage to my GPU Instance using Terraform?
+## How can I add scratch storage to my GPU Instance using Terraform/OpenTofu?
     ```
     resource “scaleway_instance_volume” “scratch_volume” {
     size_in_gb = 3000

pages/guidelines.mdx

@@ -62,7 +62,7 @@ All documentation pages must fall into one of the following categories:
 | Quickstart         | Shows how to do the main series of actions necessary to start using a Scaleway product via the console, e.g. [Instances Quickstart](/instances/quickstart/)                                   |
 | Concepts           | Defines and briefly explains the main terminology associated with a Scaleway product, e.g. [Kubernetes Concepts](/kubernetes/concepts/)                                            |
 | Troubleshooting    | Gives solutions to help resolve a common issue with a Scaleway product, e.g. [VPC auto-config is not working](/vpc/troubleshooting/autoconfig-not-working/)                          |
-| API/CLI          | Presents information and tips for creating and configuring a Scaleway product via both official and third-party APIs, CLIs, SDKs and other developer tools, e.g. Terraform, e.g. [Using Object Storage with the AWS-CLI](/object-storage/api-cli/object-storage-aws-cli/). These pages complement the [main developer reference documentation](https://www.scaleway.com/en/developers/).                           |
+| API/CLI          | Presents information and tips for creating and configuring a Scaleway product via both official and third-party APIs, CLIs, SDKs and other developer tools, e.g. Terraform/OpenTofu, e.g. [Using Object Storage with the AWS-CLI](/object-storage/api-cli/object-storage-aws-cli/). These pages complement the [main developer reference documentation](https://www.scaleway.com/en/developers/).                           |
 | Additional Content | Provides detailed information on specific subjects and features associated with a Scaleway product, e.g. [Optimize your Object Storage performance](/object-storage/reference-content/optimize-object-storage-performance/)                                            |
 | Tutorial           | Explains how to use a Scaleway product with a third-party tool, or how to use multiple Scaleway products together for a specific use-case, e.g. [Deploying Strapi on an Instance](/tutorials/strapi/)                                            |
 | FAQ                | Gives answers to the most frequently asked questions about Scaleway products, e.g. [Cockpit FAQ](/faq/cockpit/)                                            |

pages/iam/api-cli/using-api-key-object-storage.mdx

@@ -29,7 +29,7 @@ When you create new Projects, you can choose the Project in which you want to ad
 
 ## API keys
 
-You need an API key if you want to carry out actions on Scaleway products and resources via the Scaleway [API](https://www.scaleway.com/en/developers/api/) or other Scaleway developer tools like the [CLI](https://github.com/scaleway/scaleway-cli) and [Terraform](https://github.com/scaleway/terraform-provider-scaleway), or any third-party API/CLI compatible with Scaleway products. An API key is not necessary if you only use the [console](https://console.scaleway.com/) to create and manage your Scaleway resources.
+You need an API key if you want to carry out actions on Scaleway products and resources via the Scaleway [API](https://www.scaleway.com/en/developers/api/) or other Scaleway developer tools like the [CLI](https://github.com/scaleway/scaleway-cli) and [Terraform/OpenTofu](https://github.com/scaleway/terraform-provider-scaleway), or any third-party API/CLI compatible with Scaleway products. An API key is not necessary if you only use the [console](https://console.scaleway.com/) to create and manage your Scaleway resources.
 
 When you generate an API key with IAM, the key is associated with a specific [IAM user](/iam/concepts/#user) or [IAM application](/iam/concepts/#application). The API key inherits the permissions of its bearer (the user or application it is associated with). The user/application may have permissions on one or several Scaleway Projects, accorded to them via [policies](/iam/concepts/#policy).