Skip to content

Commit 750a695

Browse files
authored
Merge pull request #8212 from ovh/AG-tf-update
AG-terraform object storage-update
2 parents 750e1d3 + 35724bb commit 750a695

File tree

15 files changed

+46
-47
lines changed

15 files changed

+46
-47
lines changed

pages/storage_and_backup/object_storage/s3_terraform/guide.de-de.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,7 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4646

4747
### Configuration
4848

pages/storage_and_backup/object_storage/s3_terraform/guide.en-asia.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,7 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4646

4747
### Configuration
4848

pages/storage_and_backup/object_storage/s3_terraform/guide.en-au.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,7 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4646

4747
### Configuration
4848

pages/storage_and_backup/object_storage/s3_terraform/guide.en-ca.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,7 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4646

4747
### Configuration
4848

pages/storage_and_backup/object_storage/s3_terraform/guide.en-gb.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,7 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4646

4747
### Configuration
4848

pages/storage_and_backup/object_storage/s3_terraform/guide.en-ie.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,7 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4646

4747
### Configuration
4848

pages/storage_and_backup/object_storage/s3_terraform/guide.en-sg.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,7 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4646

4747
### Configuration
4848

pages/storage_and_backup/object_storage/s3_terraform/guide.en-us.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,7 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4646

4747
### Configuration
4848

pages/storage_and_backup/object_storage/s3_terraform/guide.es-es.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,7 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4646

4747
### Configuration
4848

pages/storage_and_backup/object_storage/s3_terraform/guide.es-us.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The “OVH provider” must be configured with a set of credentials:
2222
- an `application_secret`
2323
- a `consumer_key`
2424

25-
Why?
25+
### Why?
2626

2727
Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
2828

@@ -32,7 +32,7 @@ Once you've successfully generated your OVHcloud tokens, keep them. You'll need
3232

3333
The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
3434

35-
How do I get it?
35+
### How do I get it?
3636

3737
In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
3838

@@ -42,8 +42,7 @@ You can also use this information in Terraform resource definition files.
4242

4343
## Instructions
4444

45-
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
46-
45+
If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage){.external}
4746
### Configuration
4847

4948
First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.

0 commit comments

Comments
 (0)