chore: remove beta from all resources (#669)

Author: remyleone

docs/data-sources/lb_ip_beta.md docs/data-sources/lb_ip.md

@@ -1,23 +1,23 @@
 ---
-page_title: "Scaleway: scaleway_lb_ip_beta"
+page_title: "Scaleway: scaleway_lb_ip"
 description: |-
   Gets information about a Load Balancer IP.
 ---
 
-# scaleway_lb_ip_beta
+# scaleway_lb_ip
 
 Gets information about a Load Balancer IP.
 
 ## Example Usage
 
 ```hcl
 # Get info by IP address
-data "scaleway_lb_ip_beta" "my_ip" {
+data "scaleway_lb_ip" "my_ip" {
   ip_address = "0.0.0.0"
 }
 
 # Get info by IP ID
-data "scaleway_lb_ip_beta" "my_ip" {
+data "scaleway_lb_ip" "my_ip" {
   ip_id = "11111111-1111-1111-1111-111111111111"
 }
 ```

docs/data-sources/marketplace_image_beta.md docs/data-sources/marketplace_image.md

@@ -1,17 +1,17 @@
 ---
-page_title: "Scaleway: scaleway_marketplace_image_beta"
+page_title: "Scaleway: scaleway_marketplace_image"
 description: |-
   Gets local image ID of an image from its label name.
 ---
 
-# scaleway_marketplace_image_beta
+# scaleway_marketplace_image
 
 Gets local image ID of an image from its label name.
 
 ## Example Usage
 
 ```hcl
-data "scaleway_marketplace_image_beta" "my_image" {
+data "scaleway_marketplace_image" "my_image" {
   label  = "ubuntu_focal"
 }
 ```

docs/data-sources/registry_image_beta.md docs/data-sources/registry_image.md

@@ -1,23 +1,23 @@
 ---
-page_title: "Scaleway: scaleway_registry_image_beta"
+page_title: "Scaleway: scaleway_registry_image"
 description: |-
   Gets information about a registry image.
 ---
 
-# scaleway_registry_image_beta
+# scaleway_registry_image
 
 Gets information about a registry image.
 
 ## Example Usage
 
 ```hcl
 # Get info by image name
-data "scaleway_registry_image_beta" "my_image" {
+data "scaleway_registry_image" "my_image" {
   name = "my-image-name"
 }
 
 # Get info by image ID
-data "scaleway_registry_image_beta" "my_image" {
+data "scaleway_registry_image" "my_image" {
   image_id = "11111111-1111-1111-1111-111111111111"
   namespace_id = "11111111-1111-1111-1111-111111111111" # Optional
 }

docs/data-sources/registry_namespace_beta.md docs/data-sources/registry_namespace.md

@@ -1,23 +1,23 @@
 ---
-page_title: "Scaleway: scaleway_registry_namespace_beta"
+page_title: "Scaleway: scaleway_registry_namespace"
 description: |-
   Gets information about a registry namespace.
 ---
 
-# scaleway_registry_namespace_beta
+# scaleway_registry_namespace
 
 Gets information about a registry namespace.
 
 ## Example Usage
 
 ```hcl
 // Get info by namespace name
-data "scaleway_registry_namespace_beta" "my_namespace" {
+data "scaleway_registry_namespace" "my_namespace" {
   name = "my-namespace-name"
 }
 
 // Get info by namespace ID
-data "scaleway_registry_namespace_beta" "my_namespace" {
+data "scaleway_registry_namespace" "my_namespace" {
   namespace_id = "11111111-1111-1111-1111-111111111111"
 }
 ```

docs/resources/k8s_cluster_beta.md docs/resources/k8s_cluster.md

@@ -1,10 +1,10 @@
 ---
-page_title: "Scaleway: scaleway_k8s_cluster_beta"
+page_title: "Scaleway: scaleway_k8s_cluster"
 description: |-
   Manages Scaleway Kubernetes clusters.
 ---
 
-# scaleway_k8s_cluster_beta
+# scaleway_k8s_cluster
 
 Creates and manages Scaleway Kubernetes clusters. For more information, see [the documentation](https://developers.scaleway.com/en/products/k8s/api/).
 
@@ -13,14 +13,14 @@ Creates and manages Scaleway Kubernetes clusters. For more information, see [the
 ### Basic
 
 ```hcl
-resource "scaleway_k8s_cluster_beta" "jack" {
+resource "scaleway_k8s_cluster" "jack" {
   name = "jack"
   version = "1.18.0"
   cni = "cilium"
 }
 
-resource "scaleway_k8s_pool_beta" "john" {
-  cluster_id = scaleway_k8s_cluster_beta.jack.id
+resource "scaleway_k8s_pool" "john" {
+  cluster_id = scaleway_k8s_cluster.jack.id
   name = "john"
   node_type = "GP1-XS"
   size = 3
@@ -30,7 +30,7 @@ resource "scaleway_k8s_pool_beta" "john" {
 ### With additional configuration
 
 ```hcl
-resource "scaleway_k8s_cluster_beta" "john" {
+resource "scaleway_k8s_cluster" "john" {
   name = "john"
   description = "my awesome cluster"
   version = "1.18.0"
@@ -50,8 +50,8 @@ resource "scaleway_k8s_cluster_beta" "john" {
   }
 }
 
-resource "scaleway_k8s_pool_beta" "john" {
-  cluster_id = scaleway_k8s_cluster_beta.john.id
+resource "scaleway_k8s_pool" "john" {
+  cluster_id = scaleway_k8s_cluster.john.id
   name = "john"
   node_type = "GP1-XS"
   size = 3
@@ -65,25 +65,25 @@ resource "scaleway_k8s_pool_beta" "john" {
 ### With the kubernetes provider
 
 ```hcl
-resource "scaleway_k8s_cluster_beta" "joy" {
+resource "scaleway_k8s_cluster" "joy" {
   name = "joy"
   version = "1.18.0"
   cni = "flannel"
 }
 
-resource "scaleway_k8s_pool_beta" "john" {
-  cluster_id = scaleway_k8s_cluster_beta.joy.id
+resource "scaleway_k8s_pool" "john" {
+  cluster_id = scaleway_k8s_cluster.joy.id
   name = "john"
   node_type = "GP1-XS"
   size = 3
 }
 
 resource "null_resource" "kubeconfig" {
-    depends_on = [scaleway_k8s_pool_beta.john] # at least one pool here
+    depends_on = [scaleway_k8s_pool.john] # at least one pool here
     triggers = {
-         host = scaleway_k8s_cluster_beta.joy.kubeconfig[0].host
-         token = scaleway_k8s_cluster_beta.joy.kubeconfig[0].token
-         cluster_ca_certificate = scaleway_k8s_cluster_beta.joy.kubeconfig[0].cluster_ca_certificate
+         host = scaleway_k8s_cluster.joy.kubeconfig[0].host
+         token = scaleway_k8s_cluster.joy.kubeconfig[0].token
+         cluster_ca_certificate = scaleway_k8s_cluster.joy.kubeconfig[0].cluster_ca_certificate
     }
 }
 
@@ -183,17 +183,17 @@ In addition to all above arguments, the following attributes are exported:
 Kubernetes clusters can be imported using the `{region}/{id}`, e.g.
 
 ```bash
-$ terraform import scaleway_k8s_cluster_beta.mycluster fr-par/11111111-1111-1111-1111-111111111111
+$ terraform import scaleway_k8s_cluster.mycluster fr-par/11111111-1111-1111-1111-111111111111
 ```
 
 ## Deprecation of default_pool
 
-`default_pool` is deprecated in favour the `scaleway_k8s_pool_beta` resource. Here is a migration example.
+`default_pool` is deprecated in favour the `scaleway_k8s_pool` resource. Here is a migration example.
 
 Before:
 
 ```hcl
-resource "scaleway_k8s_cluster_beta" "jack" {
+resource "scaleway_k8s_cluster" "jack" {
   name = "jack"
   version = "1.18.0"
   cni = "cilium"
@@ -207,14 +207,14 @@ resource "scaleway_k8s_cluster_beta" "jack" {
 After:
 
 ```hcl
-resource "scaleway_k8s_cluster_beta" "jack" {
+resource "scaleway_k8s_cluster" "jack" {
   name = "jack"
   version = "1.18.0"
   cni = "cilium"
 }
 
-resource "scaleway_k8s_pool_beta" "default" {
-  cluster_id = scaleway_k8s_cluster_beta.jack.id
+resource "scaleway_k8s_pool" "default" {
+  cluster_id = scaleway_k8s_cluster.jack.id
   name = "default"
   node_type = "GP1-XS"
   size = 3
@@ -224,7 +224,7 @@ resource "scaleway_k8s_pool_beta" "default" {
 Once you have moved all the `default_pool` into their own object, you will need to import them. If your pool had the ID 11111111-1111-1111-1111-111111111111 in the `fr-par` region, you can import it by typing:
 
 ```bash
-$ terraform import scaleway_k8s_pool_beta.default fr-par/11111111-1111-1111-1111-111111111111
+$ terraform import scaleway_k8s_pool.default fr-par/11111111-1111-1111-1111-111111111111
 ```
 
 Then you will only need to type `terraform apply` to have a smooth migration.

docs/resources/k8s_pool_beta.md docs/resources/k8s_pool.md

@@ -1,10 +1,10 @@
 ---
-page_title: "Scaleway: scaleway_k8s_pool_beta"
+page_title: "Scaleway: scaleway_k8s_pool"
 description: |-
   Manages Scaleway Kubernetes cluster pools.
 ---
 
-# scaleway_k8s_pool_beta
+# scaleway_k8s_pool
 
 Creates and manages Scaleway Kubernetes cluster pools. For more information, see [the documentation](https://developers.scaleway.com/en/products/k8s/api/).
 
@@ -13,14 +13,14 @@ Creates and manages Scaleway Kubernetes cluster pools. For more information, see
 ### Basic
 
 ```hcl
-resource "scaleway_k8s_cluster_beta" "jack" {
+resource "scaleway_k8s_cluster" "jack" {
   name = "jack"
   version = "1.18.0"
   cni = "cilium"
 }
 
-resource "scaleway_k8s_pool_beta" "bill" {
-  cluster_id = scaleway_k8s_cluster_beta.jack.id
+resource "scaleway_k8s_pool" "bill" {
+  cluster_id = scaleway_k8s_cluster.jack.id
   name = "bill"
   node_type = "GP1-S"
   size = 3
@@ -90,5 +90,5 @@ In addition to all above arguments, the following attributes are exported:
 Kubernetes pools can be imported using the `{region}/{id}`, e.g.
 
 ```bash
-$ terraform import scaleway_k8s_pool_beta.mypool fr-par/11111111-1111-1111-1111-111111111111
+$ terraform import scaleway_k8s_pool.mypool fr-par/11111111-1111-1111-1111-111111111111
 ```

docs/resources/lb_beta.md docs/resources/lb.md

@@ -1,10 +1,10 @@
 ---
-page_title: "Scaleway: scaleway_lb_beta"
+page_title: "Scaleway: scaleway_lb"
 description: |-
   Manages Scaleway Load-Balancers.
 ---
 
-# scaleway_lb_beta
+# scaleway_lb
 
 -> **Note:** This terraform resource is flagged beta and might include breaking change in future releases.
 
@@ -15,11 +15,11 @@ Creates and manages Scaleway Load-Balancers. For more information, see [the docu
 ### Basic
 
 ```hcl
-resource "scaleway_lb_ip_beta" "ip" {
+resource "scaleway_lb_ip" "ip" {
 }
 
-resource "scaleway_lb_beta" "base" {
-  ip_id = scaleway_lb_ip_beta.ip.id
+resource "scaleway_lb" "base" {
+  ip_id = scaleway_lb_ip.ip.id
   region      = "fr-par"
   type        = "LB-S"
 }
@@ -56,14 +56,14 @@ In addition to all arguments above, the following attributes are exported:
 
 ## IP ID
 
-Since v1.15.0, `ip_id` is a required field. This means that now a separate `scaleway_lb_ip_beta` is required.
+Since v1.15.0, `ip_id` is a required field. This means that now a separate `scaleway_lb_ip` is required.
 When importing, the IP needs to be imported as well as the LB.
-When upgrading to v1.15.0, you will need to create a new `scaleway_lb_ip_beta` resource and import it.
+When upgrading to v1.15.0, you will need to create a new `scaleway_lb_ip` resource and import it.
 
 For instance, if you had the following:
 
 ```hcl
-resource "scaleway_lb_beta" "base" {
+resource "scaleway_lb" "base" {
   region      = "fr-par"
   type        = "LB-S"
 }
@@ -72,11 +72,11 @@ resource "scaleway_lb_beta" "base" {
 You will need to update it to:
 
 ```hcl
-resource "scaleway_lb_ip_beta" "ip" {
+resource "scaleway_lb_ip" "ip" {
 }
 
-resource "scaleway_lb_beta" "base" {
-  ip_id = scaleway_lb_ip_beta.ip.id
+resource "scaleway_lb" "base" {
+  ip_id = scaleway_lb_ip.ip.id
   region      = "fr-par"
   type        = "LB-S"
 }
@@ -85,13 +85,13 @@ resource "scaleway_lb_beta" "base" {
 And before running `terraform apply` you will need to import the IP with:
 
 ```bash
-$ terraform import scaleway_lb_ip_beta.ip fr-par/11111111-1111-1111-1111-111111111111
+$ terraform import scaleway_lb_ip.ip fr-par/11111111-1111-1111-1111-111111111111
 ```
 
 The IP ID can either be found in the console, or you can run:
 
 ```bash
-$ terraform state show scaleway_lb_beta.base
+$ terraform state show scaleway_lb.base
 ```
 
 and look for `ip_id`.
@@ -101,7 +101,7 @@ and look for `ip_id`.
 Load-Balancer can be imported using the `{region}/{id}`, e.g.
 
 ```bash
-$ terraform import scaleway_lb_beta.lb01 fr-par/11111111-1111-1111-1111-111111111111
+$ terraform import scaleway_lb.lb01 fr-par/11111111-1111-1111-1111-111111111111
 ```
 
-Be aware that you will also need to import the `scaleway_lb_ip_beta` resource.
+Be aware that you will also need to import the `scaleway_lb_ip` resource.