Merge branch 'master' into object-nightly-migration

Author: Laure-di

.github/workflows/spelling.yml

@@ -0,0 +1,19 @@
+name: Spelling
+
+permissions:
+  contents: read
+
+on: [pull_request]
+
+
+jobs:
+  spelling:
+    name: Spell Check with Typos
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Actions Repository
+        uses: actions/checkout@v4
+      - name: Spell Check Repo
+        uses: crate-ci/[email protected]
+        env:
+          CLICOLOR: 1

_typos.toml

@@ -0,0 +1,11 @@
+[files]
+extend-exclude = [
+    "**.cassette.yaml",
+    "**.go",
+    "CHANGELOG.md",
+    "go.mod"
+]
+
+[default.extend-words]
+pn = "pn"
+thi = "thi"

docs/data-sources/object.md

@@ -0,0 +1,55 @@
+---
+subcategory: "Object Storage"
+page_title: "Scaleway: scaleway_object"
+---
+
+# scaleway_object
+
+The `scaleway_object` data source is used to retrieve information about an Object Storage object.
+
+Refer to the Object Storage [documentation](https://www.scaleway.com/en/docs/object-storage/how-to/create-a-bucket/) for more information.
+
+## Retrieve an Object Storage object
+
+The following example demonstrates how to retrieve metadata about an object stored in a bucket:
+
+```hcl
+resource "scaleway_object_bucket" "main" {
+  name = "bucket.test.com"
+}
+
+resource "scaleway_object" "example" {
+  bucket = scaleway_object_bucket.main.name
+  key    = "example.txt"
+  content = "Hello world!"
+}
+
+data "scaleway_object" "selected" {
+  bucket = scaleway_object.example.bucket
+  key    = scaleway_object.example.key
+}
+```
+
+## Argument Reference
+
+This section lists the arguments that you can provide to the `scaleway_object` data source to filter and retrieve the desired Object Storage bucket. Each argument has a specific purpose:
+
+## Argument Reference
+
+This section lists the arguments that you can provide to the `scaleway_object` data source to filter and retrieve the desired Object Storage bucket. Each argument has a specific purpose:
+
+- `bucket` - (Required) The name of the bucket, or its terraform ID (`{region}/{name}`)
+- `key` - (Required) The key (path or filename) of the object within the bucket.
+- `region` - (Defaults to [provider](../index.md#region) `region`) The [region](../guides/regions_and_zones.md#zones) in which the bucket exists.
+- `project_id` - (Defaults to [provider](../index.md#project_id) `project_id`) The ID of the project with which the bucket is associated.
+
+## Attributes Reference
+
+The `scaleway_object` data source exports certain attributes once the object information is retrieved. These attributes can be referenced in other parts of your Terraform configuration.
+
+In addition to all above arguments, the following attribute is exported:
+
+* `id` - The unique identifier of the object.
+
+~> **Important**: Object IDs are regional, and follow the format {region}/{bucket}/{key}, e.g. fr-par/bucket-name/example.txt.
+

docs/guides/regions_and_zones.md

@@ -6,7 +6,7 @@ page_title: "Scaleway Zones and Regions"
 
 Scaleway's products are deployed across multiple datacenter in the world.
 
-For technical and legal reasons, some products are splitted by Region or by Availability Zones.
+For technical and legal reasons, some products are split by Region or by Availability Zones.
 When using such product, you can choose the location that better fits your need (country, latency, ...).
 
 ## Regions

docs/resources/block_snapshot.md

@@ -97,7 +97,7 @@ In addition to all arguments above, the following attributes are exported:
 
 - `id` - The ID of the snapshot.
 
-~> **Important:** The IDs of Block Storage volumes snapshots are [zoned](../guides/regions_and_zones.md#resource-ids), meaning that the zone is part of the ID, in the form `{zone}/{id}`. For example, a snapshot ID migt be `fr-par-1/11111111-1111-1111-1111-111111111111`.
+~> **Important:** The IDs of Block Storage volumes snapshots are [zoned](../guides/regions_and_zones.md#resource-ids), meaning that the zone is part of the ID, in the form `{zone}/{id}`. For example, a snapshot ID might be `fr-par-1/11111111-1111-1111-1111-111111111111`.
 
 ## Import
 

docs/resources/cockpit_grafana_user.md

@@ -34,7 +34,7 @@ This section lists the arguments that are supported:
 
 - `login` - (Required) The username of the Grafana user. The `admin` user is not yet available for creation. You need your Grafana username to log in to Grafana and access your dashboards.
 - `role` - (Required) The role assigned to the Grafana user. Must be `editor` or `viewer`.
-- `project_id` - (Defaults to Project ID speficied in the [provider configuration](../index.md#project_id)) The ID of the Project the Cockpit is associated with.
+- `project_id` - (Defaults to Project ID specified in the [provider configuration](../index.md#project_id)) The ID of the Project the Cockpit is associated with.
 
 ## Attributes Reference
 

docs/resources/domain_record.md

@@ -13,7 +13,7 @@ Refer to the Domains and DNS [product documentation](https://www.scaleway.com/en
 
 ### Create basic DNS records
 
-The folllowing commands allow you to:
+The following commands allow you to:
 
 - create an A record for the `www.domain.tld` domain, pointing to `1.2.3.4` and another one pointing to `1.2.3.5`
 
@@ -57,7 +57,7 @@ resource "scaleway_domain_record" "mx2" {
 
 ### Create dynamic records
 
-The folllowing commands allow you to:
+The following commands allow you to:
 
 - create a Geo IP record for `images.domain.tld` that points to different IPs based on the user's location: `1.2.3.5` for users in France (EU), and `4.3.2.1` for users in North America (NA)
 

docs/resources/iot_hub.md

@@ -30,7 +30,7 @@ The following arguments are supported:
 
 ~> **Important:** Updates to `product_plan` will recreate the IoT Hub Instance.
 
-- `enabled` - (Optional) Wether the IoT Hub instance should be enabled or not.
+- `enabled` - (Optional) Whether the IoT Hub instance should be enabled or not.
 
 ~> **Important:** Updates to `enabled` will disconnect eventually connected devices.
 
@@ -54,7 +54,7 @@ In addition to all arguments above, the following attributes are exported:
 - `device_count` - The number of registered devices in the Hub.
 - `connected_device_count` - The current number of connected devices in the Hub.
 - `mqtt_ca_url` - The MQTT ca url
-- `mqtt_ca` - The MQTT certificat content
+- `mqtt_ca` - The MQTT certificate content
 
 
 ## Import

docs/resources/ipam_ip.md

@@ -115,7 +115,7 @@ The following arguments are supported:
     - `private_network_id` - The Private Network of the IP (if the IP is a private IP).
     - `subnet_id` - The Private Network subnet of the IP (if the IP is a private IP).
 - `is_ipv6` - (Optional) Defines whether to request an IPv6 address instead of IPv4.
-- `custome_resource` - (Optional) The custom resource to attach to the IP being reserved. An example of a custom resource is a virtual machine hosted on an Elastic Metal server.
+- `custom_resource` - (Optional) The custom resource to attach to the IP being reserved. An example of a custom resource is a virtual machine hosted on an Elastic Metal server.
     - `mac_address` - The MAC address of the custom resource.
     - `name` - When the resource is in a Private Network, a DNS record is available to resolve the resource name.
 - `region` - (Defaults to [provider](../index.md#region) `region`) The [region](../guides/regions_and_zones.md#regions) of the IP.

docs/resources/k8s_pool.md

@@ -56,7 +56,7 @@ The following arguments are supported:
 
 - `tags` - (Optional) The tags associated with the pool.
 
--> Note: As mentionned in [this document](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/tags.md#taints), taints of a pool's nodes are applied using tags. (e.g.: `"taint=taintName=taintValue:Effect"`)
+-> Note: As mentioned in [this document](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/tags.md#taints), taints of a pool's nodes are applied using tags. (e.g.: `"taint=taintName=taintValue:Effect"`)
 
 - `placement_group_id` - (Optional) The [placement group](https://www.scaleway.com/en/developers/api/instance/#path-placement-groups-create-a-placement-group) the nodes of the pool will be attached to.