doc(object): document project ID for bucket child resources

docs/data-sources/object_bucket_policy.md

@@ -19,8 +19,12 @@ data "scaleway_object_bucket_policy" "main" {
 ## Argument Reference
 
 - `bucket` - (Required) The bucket name.
-- `region` - (Defaults to [provider](../index.md#region) `region`) The [region](../guides/regions_and_zones.md#zones) in which the Object Storage exists.
-- `project_id` - (Defaults to [provider](../index.md#project_id) `project_id`) The ID of the project the bucket is associated with.
+- `region` - (Defaults to [provider](../index.md#arguments-reference) `region`) The [region](../guides/regions_and_zones.md#zones) in which the Object Storage exists.
+- `project_id` - (Defaults to [provider](../index.md#arguments-reference) `project_id`) The ID of the project the bucket is associated with.
+
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the `project_id` for every child resource of the bucket,
+like bucket policies. Otherwise, Terraform will try to create the child resource with the default project ID and you will get a 403 error.
 
 
 ## Attributes Reference

docs/index.md

@@ -131,8 +131,8 @@ The Scaleway provider offers three ways of providing these credentials.
 The following methods are supported, in this priority order:
 
 1. [Environment variables](#environment-variables)
-1. [Static credentials](#static-credentials)
-1. [Shared configuration file](#shared-configuration-file)
+2. [Static credentials](#static-credentials)
+3. [Shared configuration file](#shared-configuration-file)
 
 ### Environment variables
 
@@ -154,7 +154,7 @@ $ terraform plan
 
 ### Static credentials
 
-!> **Warning**: Hard-coding credentials into any Terraform configuration is not recommended, and risks secret leakage should this file ever be committed to a public version control system.
+~> **Warning**: Hard-coding credentials into any Terraform configuration is not recommended, and risks secret leakage should this file ever be committed to a public version control system.
 
 Static credentials can be provided by adding `access_key` and `secret_key` attributes in-line in the Scaleway provider block:
 

docs/resources/object.md

@@ -41,6 +41,11 @@ The following arguments are supported:
 * `tags` - (Optional) Map of tags
 * `project_id` - (Defaults to [provider](../index.md#arguments-reference) `project_id`) The ID of the project the bucket is associated with.
 
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the `project_id` for every child resource of the bucket,
+like objects. Otherwise, Terraform will try to create the child resource with the default project ID and you will get a 403 error.
+
+
 ## Attributes Reference
 
 In addition to all arguments above, the following attribute is exported:
@@ -58,3 +63,10 @@ Objects can be imported using the `{region}/{bucketName}/{objectKey}` identifier
 ```bash
 $ terraform import scaleway_object.some_object fr-par/some-bucket/some-file
 ```
+
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the project ID at the end of the import command.
+
+```bash
+$ terraform import scaleway_object.some_object fr-par/some-bucket/some-file@xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
+```

docs/resources/object_bucket_acl.md

@@ -69,6 +69,10 @@ The following arguments are supported:
 * `region` - (Optional) The [region](https://developers.scaleway.com/en/quickstart/#region-definition) in which the bucket should be created.
 * `project_id` - (Defaults to [provider](../index.md#arguments-reference) `project_id`) The ID of the project the bucket is associated with.
 
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the `project_id` for every child resource of the bucket,
+like bucket ACLs. Otherwise, Terraform will try to create the child resource with the default project ID and you will get a 403 error.
+
 
 ## The ACL
 
@@ -118,8 +122,15 @@ In addition to all arguments above, the following attributes are exported:
 
 ## Import
 
-Buckets can be imported using the `{region}/{bucketName}/{acl}` identifier, e.g.
+Bucket ACLs can be imported using the `{region}/{bucketName}/{acl}` identifier, e.g.
+
+```bash
+$ terraform import scaleway_object_bucket_acl.some_bucket fr-par/some-bucket/private
+```
+
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the project ID at the end of the import command.
 
 ```bash
-$ terraform import scaleway_object_bucket_acl.some_bucket fr-par/some-bucket
-/private```
+$ terraform import scaleway_object_bucket_acl.some_bucket fr-par/some-bucket/private@xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
+```

docs/resources/object_bucket_lock_configuration.md

@@ -56,6 +56,10 @@ The following arguments are supported:
 
 - `project_id` - (Defaults to [provider](../index.md#arguments-reference) `project_id`) The ID of the project the bucket is associated with.
 
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the `project_id` for every child resource of the bucket,
+like object lock configurations. Otherwise, Terraform will try to create the child resource with the default project ID and you will get a 403 error.
+
 ## Attributes Reference
 
 In addition to all arguments above, the following attributes are exported:
@@ -66,8 +70,15 @@ In addition to all arguments above, the following attributes are exported:
 
 ## Import
 
-Lock configuration Bucket can be imported using the `{region}/{bucketName}` identifier, e.g.
+Bucket lock configurations can be imported using the `{region}/{bucketName}` identifier, e.g.
 
 ```bash
 $ terraform import scaleway_object_bucket_lock_configuration.some_bucket fr-par/some-bucket
 ```
+
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the project ID at the end of the import command.
+
+```bash
+$ terraform import scaleway_object_bucket_lock_configuration.some_bucket fr-par/some-bucket@xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
+```

docs/resources/object_bucket_policy.md

@@ -224,6 +224,10 @@ The following arguments are supported:
 * `policy` - (Required) The policy document. This is a JSON formatted string. For more information about building AWS IAM policy documents with Terraform, see the [AWS IAM Policy Document Guide](https://learn.hashicorp.com/tutorials/terraform/aws-iam-policy?_ga=2.164714495.1557487853.1659960650-563504983.1635944492).
 * `project_id` - (Defaults to [provider](../index.md#arguments-reference) `project_id`) The ID of the project the bucket is associated with.
 
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the `project_id` for every child resource of the bucket,
+like bucket policies. Otherwise, Terraform will try to create the child resource with the default project ID and you will get a 403 error.
+
 ~> **Important:** The [aws_iam_policy_document](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document) data source may be used, so long as it specifies a principal.
 
 ## Attributes Reference
@@ -238,8 +242,15 @@ In addition to all arguments above, the following attribute is exported:
 
 ## Import
 
-Buckets can be imported using the `{region}/{bucketName}` identifier, e.g.
+Bucket policies can be imported using the `{region}/{bucketName}` identifier, e.g.
 
 ```bash
 $ terraform import scaleway_object_bucket_policy.some_bucket fr-par/some-bucket
 ```
+
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the project ID at the end of the import command.
+
+```bash
+$ terraform import scaleway_object_bucket_policy.some_bucket fr-par/some-bucket@xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
+```

docs/resources/object_bucket_website_configuration.md

@@ -71,6 +71,10 @@ The following arguments are supported:
 * `error_document` - (Optional) The name of the error document for the website [detailed below](#error_document).
 * `project_id` - (Defaults to [provider](../index.md#arguments-reference) `project_id`) The ID of the project the bucket is associated with.
 
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the `project_id` for every child resource of the bucket,
+like bucket website configurations. Otherwise, Terraform will try to create the child resource with the default project ID and you will get a 403 error.
+
 ### index_document
 
 The `index_document` configuration block supports the following arguments:
@@ -97,8 +101,15 @@ The error_document configuration block supports the following arguments:
 
 ## Import
 
-Website configuration Bucket can be imported using the `{region}/{bucketName}` identifier, e.g.
+Bucket website configurations can be imported using the `{region}/{bucketName}` identifier, e.g.
 
 ```bash
 $ terraform import scaleway_object_bucket_website_configuration.some_bucket fr-par/some-bucket
 ```
+
+~> **Important:** The `project_id` attribute has a particular behavior with s3 products because the s3 API is scoped by project.
+If you are using a project different from the default one, you have to specify the project ID at the end of the import command.
+
+```bash
+$ terraform import scaleway_object_bucket_website_configuration.some_bucket fr-par/some-bucket@xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
+```