You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`scaleway_block_snapshot` is used to retrieve information about a Block Storage volume snapshot.
8
+
The `scaleway_block_snapshot` data source is used to retrieve information about a Block Storage volume snapshot.
9
9
10
10
Refer to the Block Storage [product documentation](https://www.scaleway.com/en/docs/storage/block/) and [API documentation](https://www.scaleway.com/en/developers/api/block/) for more information.
11
11
12
12
## Retrieve a volume's snapshot
13
13
14
-
The following commands allow you to retrieve information about a Block Storage volume snapshot, using several methods:
14
+
The following commands allow you to:
15
15
16
16
- retrieve a snapshot specified by its name
17
17
- retrieve a snapshot specified by its name and the ID of the Block Storage volume it is associated with
Copy file name to clipboardexpand all lines: docs/data-sources/block_volume.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Refer to the Block Storage [product documentation](https://www.scaleway.com/en/d
10
10
11
11
## Retrieve a Block Storage volume
12
12
13
-
The following commands allow you to retrieve information about a Block Storage volume, using two methods:
13
+
The following commands allow you to:
14
14
15
15
- retrieve a Block Storage volume specified by its name
16
16
- retrieve a Block Storage volume specified by its ID
@@ -30,7 +30,7 @@ data "scaleway_block_volume" "my_volume" {
30
30
31
31
## Arguments reference
32
32
33
-
This section lists the arguments that you can provide to the `scaleway_block_volume` data source to filter and retrieve the desired volume. Each argument has a specific purpose:
33
+
This section lists the arguments that you can provide to the `scaleway_block_volume` data source to filter and retrieve the desired volume.
34
34
35
35
-`volume_id` - (Optional) The unique identifier of the volume. Only one of `name` and `volume_id` should be specified.
36
36
-`name` - (Optional) The name of the volume. Only one of `name` and `volume_id` should be specified.
Copy file name to clipboardexpand all lines: docs/data-sources/cockpit.md
+4-2
Original file line number
Diff line number
Diff line change
@@ -36,14 +36,16 @@ data "scaleway_cockpit" "main" {
36
36
37
37
## Arguments reference
38
38
39
-
-`project_id` - Specifies the ID of the Scaleway Project that the Cockpit is associated with. If not specified, it defaults to the [provider's](../index.md#project_id)`project_id`.
39
+
This section lists the arguments that you can provide to the `scaleway_cockpit` data source to filter and retrieve the desired Cockpit.
40
+
41
+
-`project_id` - Specifies the ID of the Scaleway Project that the Cockpit is associated with. If not specified, it defaults to the Project ID specified in the [provider configuration](../index.md#project_id).
40
42
41
43
-`plan` - (Optional) Specifies the name or ID of the pricing plan to use.
42
44
43
45
44
46
## Attributes reference
45
47
46
-
In addition to all arguments above, the following attributes are exported:
48
+
The `scaleway_cockpit` data source exports certain attributes once the Cockpit information is retrieved. These attributes can be referenced in other parts of your Terraform configuration.
47
49
48
50
-`plan_id` - (Deprecated) ID of the current pricing plan
49
51
-`endpoints` - (Deprecated) A list of [endpoints](https://www.scaleway.com/en/docs/observability/cockpit/concepts/#endpoints) related to Cockpit, each with specific URLs:
The page provides documentation for `scaleway_cockpit_plan`, which is used to fetch details about a specific Scaleway Cockpit pricing plan by its name. This information can then be used to configure resources like `scaleway_cockpit`.
7
+
The `scaleway_cockpit_plan` data source is used to fetch details about a specific Scaleway Cockpit pricing plan. This information can then be used to configure resources like `scaleway_cockpit`.
8
8
9
9
Find out more about [pricing plans](https://console.scaleway.com/cockpit/plans) in the Scaleway console.
10
10
11
+
Refer to Cockpit's [product documentation](https://www.scaleway.com/en/docs/observability/cockpit/concepts/) and [API documentation](https://www.scaleway.com/en/developers/api/cockpit/regional-api) for more information.
12
+
11
13
## Fetch and associate a pricing plan to a Cockpit
12
14
13
15
The following command shows how to fetch information about the `premium` pricing plan and how to associate it with the Cockpit of your Scaleway default Project.
Copy file name to clipboardexpand all lines: docs/data-sources/domain_record.md
+4-6
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Refer to the Domains and DNS [product documentation](https://www.scaleway.com/en
12
12
13
13
## Query domain records
14
14
15
-
The following commands allow you to query domain records using two methods:
15
+
The following commands allow you to:
16
16
17
17
- query a domain record specified by the DNS zone (`domain.tld`), the record name (`www`), the record type (`A`), and the record content (`1.2.3.4`).
18
18
- query a domain record specified by the DNS zone (`domain.tld`) and the unique record ID (`11111111-1111-1111-1111-111111111111`).
@@ -35,7 +35,7 @@ data "scaleway_domain_record" "by_id" {
35
35
36
36
## Arguments reference
37
37
38
-
This section lists the arguments that can be provided to the `scaleway_domain_record` data source:
38
+
This section lists the arguments that you can provide to the `scaleway_domain_record` data source to filter and retrieve the desired record:
39
39
40
40
-`dns_zone` - (Optional) The DNS zone (domain) to which the record belongs. This is a required field in both examples above but is optional in the context of defining the data source.
41
41
@@ -47,13 +47,11 @@ This section lists the arguments that can be provided to the `scaleway_domain_re
47
47
48
48
-`record_id` - (Optional) The unique identifier of the record. Cannot be used with `name`, `type`, and `data`.
49
49
50
-
-`project_id` - (Defaults to the Project ID specified in the [provider configuration](../index.md#project_id)). The ID of the project associated with the domain.
50
+
-`project_id` - (Defaults to the Project ID specified in the [provider configuration](../index.md#project_id)). The ID of the Project associated with the domain.
51
51
52
52
## Attributes reference
53
53
54
-
This section lists the attributes that are exported by the scaleway_domain_record data source. These attributes can be referenced in other parts of your Terraform configuration:
55
-
56
-
In addition to all arguments above, the following attributes are exported:
54
+
This section lists the attributes that are exported when the `scaleway_domain_record` data source is created. These attributes can be referenced in other parts of your Terraform configuration:
The `scaleway_domain_record` data source is used to get information about a DNS zone within a specific domain and subdomain in Scaleway Domains and DNS.
8
+
The `scaleway_domain_zone` data source is used to get information about a DNS zone within a specific domain and subdomain in Scaleway Domains and DNS.
9
9
10
10
Refer to the Domains and DNS [product documentation](https://www.scaleway.com/en/docs/network/domains-and-dns/) and [API documentation](https://www.scaleway.com/en/developers/api/domains-and-dns/) for more information.
11
11
@@ -23,20 +23,20 @@ data "scaleway_domain_zone" "main" {
23
23
24
24
## Arguments reference
25
25
26
-
This section lists the arguments that can be provided to the `scaleway_domain_record` data source:
26
+
This section lists the arguments that you can provide to the `scaleway_domain_zone` data source to filter and retrieve the desired DNS zone:
27
27
28
28
29
29
-`domain` - (Required) The primary domain name where the DNS zone is located. This is a mandatory field.
30
30
31
31
-`subdomain` - (Required) The subdomain (or zone name) within the primary domain. This is a mandatory field.
32
32
33
-
-`project_id` - ([Defaults to the provider's](../index.md#project_id)`project_id`). The ID of the Scaleway Project associated with the domain. If not specified, it defaults to the `project_id` set in the provider configuration.
33
+
-`project_id` - (Defaults to Project ID specified in [the provider configuration](../index.md#project_id)). The ID of the Scaleway Project associated with the domain. If not specified, it defaults to the `project_id` set in the provider configuration.
34
34
35
35
## Attributes reference
36
36
37
-
This section lists the attributes that are exported by the `scaleway_domain_zone` data source. These attributes can be referenced in other parts of your Terraform configuration:
37
+
This section lists the attributes that are exported when the `scaleway_domain_zone` data source is created. These attributes can be referenced in other parts of your Terraform configuration:
38
38
39
-
-`id` - The unique identifier of the zone, formatted as`{subdomain}.{domain}`.
39
+
-`id` - The unique identifier of the zone, in the`{subdomain}.{domain}` format.
Copy file name to clipboardexpand all lines: docs/data-sources/secret.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -9,13 +9,13 @@ The `scaleway_secret` data source is used to get information about a specific se
9
9
10
10
Refer to the Secret Manager [product documentation](https://www.scaleway.com/en/docs/identity-and-access-management/secret-manager/) and [API documentation](https://www.scaleway.com/en/developers/api/secret-manager/) for more information.
11
11
12
-
## Crrate a secret and get its information
12
+
## Create a secret and get its information
13
13
14
-
The following commands show you how to:
14
+
The following commands allow you to:
15
15
16
16
- create a secret named `foo` with the description `barr`
17
-
- retrieve the secret information using the secret's ID
18
-
- retrieve the secret information using the secret's name
17
+
- retrieve the secret's information using the secret's ID
18
+
- retrieve the secret's information using the secret's name
19
19
20
20
```hcl
21
21
// Create a secret
@@ -37,7 +37,7 @@ data "scaleway_secret" "by_name" {
37
37
38
38
## Arguments reference
39
39
40
-
This section lists the arguments that can be provided to the `scaleway_secret` data source:
40
+
This section lists the arguments that you can provide to the `scaleway_secret` data source to filter and retrieve the desired secret:
This section lists the arguments that can be provided to the `scaleway_secret_version` data source:
66
+
This section lists the arguments that you can provide to the `scaleway_secret_version` data source to filter and retrieve the desired version:
67
67
68
68
-`secret_id` - (Optional) The ID of the secret associated with the secret version. Only one of `secret_id` and `secret_name` should be specified.
69
69
@@ -85,10 +85,10 @@ see [Sensitive Data in State](https://developer.hashicorp.com/terraform/language
85
85
86
86
## Attributes reference
87
87
88
-
This section lists the attributes that are exported when the `scaleway_secret_version` data source is created:
88
+
This section lists the attributes that are exported by the `scaleway_secret_version` data source. These attributes can be referenced in other parts of your Terraform configuration:
89
89
90
90
-`description` - (Optional) The description of the secret version (e.g. `my-new-description`).
91
-
-`data` - The data payload of the secret version. This is a sensitive attribute containing the secret value. Learn more in the [data section](#data)
91
+
-`data` - The data payload of the secret version. This is a sensitive attribute containing the secret value. Learn more in the [data section](#data).
92
92
-`status` - The status of the secret version.
93
93
-`created_at` - The date and time of the secret version's creation in RFC 3339 format.
94
94
-`updated_at` - The date and time of the secret version's last update in RFC 3339 format.
This section lists the arguments that are supported:
32
32
33
33
-`volume_id` - (Optional) The ID of the volume to take a snapshot from.
34
34
-`name` - (Optional) The name of the snapshot. If not provided, a name will be randomly generated.
35
-
-`zone` - (Defaults to the zone specified in the [provider's configuration](../index.md#zone)). The [zone](../guides/regions_and_zones.md#zones) in which the snapshot should be created.
36
-
-`project_id` - (Defaults to the Project ID specified in the [provider's configuration](../index.md#project_id)). The ID of the Scaleway Project the snapshot is associated with.
35
+
-`zone` - (Defaults to the zone specified in the [provider configuration](../index.md#zone)). The [zone](../guides/regions_and_zones.md#zones) in which the snapshot should be created.
36
+
-`project_id` - (Defaults to the Project ID specified in the [provider configuration](../index.md#project_id)). The ID of the Scaleway Project the snapshot is associated with.
37
37
-`tags` - (Optional) A list of tags to apply to the snapshot.
38
38
39
39
## Attributes reference
40
40
41
-
This section lists the attributes that are exported by the `scaleway_block_snapshot` resource:
41
+
This section lists the attributes that are exported when the `scaleway_block_snapshot` resource is created:
42
42
43
43
-`id` - The ID of the snapshot.
44
44
45
45
~> **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`.
46
46
47
47
## Import
48
48
49
-
This section explains how to import the snapshot of a Block Storage volume using the zoned ID format:
50
-
51
-
The following command shows you how to import snapshots using the `{zone}/{id}` format.
49
+
This section explains how to import the snapshot of a Block Storage volume using the zoned ID format (`{zone}/{id}`).
Copy file name to clipboardexpand all lines: docs/resources/block_volume.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Refer to the Block Storage [product documentation](https://www.scaleway.com/en/d
11
11
12
12
## Create a Block Storage volume
13
13
14
-
The following command shows you how to create a Block Storage volume of 20 GB with the desired[IOPS](https://www.scaleway.com/en/docs/storage/block/concepts/#iops).
14
+
The following command allows you to create a Block Storage volume of 20 GB with a 5000[IOPS](https://www.scaleway.com/en/docs/storage/block/concepts/#iops).
This section lists the arguments that can be provided to the `scaleway_block_volume` resource:
49
+
This section lists the arguments that are supported:
50
50
51
51
-`iops` - (Required) The maximum [IOPs](https://www.scaleway.com/en/docs/storage/block/concepts/#iops) expected, must match available options.
52
52
-`name` - (Optional) The name of the volume. If not provided, a name will be randomly generated.
53
53
-`size_in_gb` - (Optional) The size of the volume in gigabytes. Only one of `size_in_gb`, and `snapshot_id` should be specified.
54
54
-`snapshot_id` - (Optional) If set, the new volume will be created from this snapshot. Only one of `size_in_gb`, `snapshot_id` should be specified.
55
55
-`tags` - (Optional) A list of tags to apply to the volume.
56
-
-`zone` - (Defaults to the zone specified in the [provider's configuration](../index.md#zone)). The [zone](../guides/regions_and_zones.md#zones) in which the volume should be created.
57
-
-`project_id` - (Defaults to the Project ID specified in the [provider's configurqtion](../index.md#project_id)). The ID of the Project the volume is associated with.
56
+
-`zone` - (Defaults to the zone specified in the [provider configuration](../index.md#zone)). The [zone](../guides/regions_and_zones.md#zones) in which the volume should be created.
57
+
-`project_id` - (Defaults to the Project ID specified in the [provider configurqtion](../index.md#project_id)). The ID of the Project the volume is associated with.
58
58
59
59
## Attributes reference
60
60
61
61
This section lists the attributes that are exported when the `scaleway_block_volume` resource is created:
62
62
63
63
-`id` - The ID of the volume.
64
64
65
-
~> **Important:** The IDs of Block Storage volumes 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 volume ID migt be`fr-par-1/11111111-1111-1111-1111-111111111111`.
65
+
~> **Important:** The IDs of Block Storage volumes are [zoned](../guides/regions_and_zones.md#resource-ids), meaning that the zone is part of the ID, in the `{zone}/{id}` format. For example, a volume ID might look like the following:`fr-par-1/11111111-1111-1111-1111-111111111111`.
66
66
67
67
-`organization_id` - The Organization ID the volume is associated with.
Copy file name to clipboardexpand all lines: docs/resources/cockpit.md
+12-5
Original file line number
Diff line number
Diff line change
@@ -13,11 +13,18 @@ The `scaleway_cockpit` resource allows you to create and manage Scaleway Cockpit
13
13
14
14
Refer to Cockpit's [product documentation](https://www.scaleway.com/en/docs/observability/cockpit/concepts/) and [API documentation](https://www.scaleway.com/en/developers/api/cockpit/regional-api) for more information.
15
15
16
-
For more information consult the [documentation](https://www.scaleway.com/en/docs/observability/cockpit/concepts/).
17
-
18
16
## Use Cockpit
19
17
18
+
<<<<<<< HEAD
20
19
### Manage Cockpit in the Scaleway default Project
20
+
=======
21
+
The following commands allow you to:
22
+
23
+
- activate Cockpit in the Scaleway default Project
24
+
- activate Cockpit in a given Project specified by the Project ID
-`project_id` - - `project_id` - (Defaults to the Project specified in the [provider's configuration](../index.md#project_id)) The ID of the Project the Cockpit is associated with.
76
+
-`project_id` - (Defaults to the Project specified in the [provider's configuration](../index.md#project_id)) The ID of the Project the Cockpit is associated with.
70
77
-`plan` - (Optional) Name of the plan to use. Available plans are: free, premium, and custom.
71
78
72
79
## Attributes reference
73
80
74
-
This section lists the attributes that are automatically exported when the `scaleway_cockpit` resource is created:
81
+
This section lists the attributes that are exported when the `scaleway_cockpit` resource is created:
75
82
76
83
-`plan_id` - (Deprecated) The ID of the current pricing plan.
77
84
-`endpoints` - (Deprecated) A list of [endpoints](https://www.scaleway.com/en/docs/observability/cockpit/concepts/#endpoints) related to Cockpit, each with specific URLs:
@@ -83,7 +90,7 @@ This section lists the attributes that are automatically exported when the `scal
83
90
84
91
## Import
85
92
86
-
This section explains how to import Cockpits using its `{project_id}`:
93
+
This section explains how to import a Cockpit using its `{project_id}`.
0 commit comments