chore(provider): move import examples to respective files

docs/resources/affinity_group.md

@@ -87,12 +87,6 @@ resource "stackit_affinity_group" "example" {
   name       = "example-affinity-group-name"
   policy     = "hard-anti-affinity"
 }
-
-# Only use the import statement, if you want to import an existing affinity group
-import {
-  to = stackit_affinity_group.import-example
-  id = "${var.project_id},${var.region},${var.affinity_group_id}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -113,3 +107,17 @@ import {
 - `affinity_group_id` (String) The affinity group ID.
 - `id` (String) Terraform's internal resource identifier. It is structured as "`project_id`,`region`,`affinity_group_id`".
 - `members` (List of String) The servers that are part of the affinity group.
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing affinity group
+import {
+  to = stackit_affinity_group.import-example
+  id = "${var.project_id},${var.region},${var.affinity_group_id}"
+}
+```

docs/resources/authorization_folder_custom_role.md

@@ -27,12 +27,6 @@ resource "stackit_authorization_folder_custom_role" "example" {
     "iam.subject.get"
   ]
 }
-
-# Only use the import statement, if you want to import an existing custom role
-import {
-  to = stackit_authorization_folder_custom_role.import-example
-  id = "${var.folder_id},${var.custom_role_id}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -49,3 +43,17 @@ import {
 
 - `id` (String) Terraform's internal resource identifier. It is structured as "[resource_id],[role_id]".
 - `role_id` (String) The ID of the role.
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing custom role
+import {
+  to = stackit_authorization_folder_custom_role.import-example
+  id = "${var.folder_id},${var.custom_role_id}"
+}
+```

docs/resources/authorization_folder_role_assignment.md

@@ -28,12 +28,6 @@ resource "stackit_authorization_folder_role_assignment" "fra" {
   role        = "reader"
   subject     = "foo.bar@stackit.cloud"
 }
-
-# Only use the import statement, if you want to import an existing folder role assignment
-import {
-  to = stackit_authorization_folder_role_assignment.import-example
-  id = "${var.folder_id},${var.folder_role_assignment},${var.folder_role_assignment_subject}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -48,3 +42,17 @@ import {
 ### Read-Only
 
 - `id` (String) Terraform's internal resource identifier. It is structured as "`resource_id`,`role`,`subject`".
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing folder role assignment
+import {
+  to = stackit_authorization_folder_role_assignment.import-example
+  id = "${var.folder_id},${var.folder_role_assignment},${var.folder_role_assignment_subject}"
+}
+```

docs/resources/authorization_organization_custom_role.md

@@ -21,12 +21,6 @@ resource "stackit_authorization_organization_custom_role" "example" {
     "iam.subject.get"
   ]
 }
-
-# Only use the import statement, if you want to import an existing custom role
-import {
-  to = stackit_authorization_organization_custom_role.import-example
-  id = "${var.organization_id},${var.custom_role_id}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -43,3 +37,17 @@ import {
 
 - `id` (String) Terraform's internal resource identifier. It is structured as "[resource_id],[role_id]".
 - `role_id` (String) The ID of the role.
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing custom role
+import {
+  to = stackit_authorization_organization_custom_role.import-example
+  id = "${var.organization_id},${var.custom_role_id}"
+}
+```

docs/resources/authorization_organization_role_assignment.md

@@ -21,12 +21,6 @@ resource "stackit_authorization_organization_role_assignment" "example" {
   role        = "owner"
   subject     = "john.doe@stackit.cloud"
 }
-
-# Only use the import statement, if you want to import an existing organization role assignment
-import {
-  to = stackit_authorization_organization_role_assignment.import-example
-  id = "${var.organization_id},${var.org_role_assignment_role},${var.org_role_assignment_subject}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -41,3 +35,17 @@ import {
 ### Read-Only
 
 - `id` (String) Terraform's internal resource identifier. It is structured as "`resource_id`,`role`,`subject`".
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing organization role assignment
+import {
+  to = stackit_authorization_organization_role_assignment.import-example
+  id = "${var.organization_id},${var.org_role_assignment_role},${var.org_role_assignment_subject}"
+}
+```

docs/resources/authorization_project_custom_role.md

@@ -27,12 +27,6 @@ resource "stackit_authorization_project_custom_role" "example" {
     "iam.subject.get"
   ]
 }
-
-# Only use the import statement, if you want to import an existing custom role
-import {
-  to = stackit_authorization_project_custom_role.import-example
-  id = "${var.project_id},${var.custom_role_id}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -49,3 +43,17 @@ import {
 
 - `id` (String) Terraform's internal resource identifier. It is structured as "[resource_id],[role_id]".
 - `role_id` (String) The ID of the role.
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing custom role
+import {
+  to = stackit_authorization_project_custom_role.import-example
+  id = "${var.project_id},${var.custom_role_id}"
+}
+```

docs/resources/authorization_project_role_assignment.md

@@ -28,12 +28,6 @@ resource "stackit_authorization_project_role_assignment" "pra" {
   role        = "reader"
   subject     = "foo.bar@stackit.cloud"
 }
-
-# Only use the import statement, if you want to import an existing project role assignment
-import {
-  to = stackit_authorization_project_role_assignment.import-example
-  id = "${var.project_id},${var.project_role_assignment_role},${var.project_role_assignment_subject}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -48,3 +42,17 @@ import {
 ### Read-Only
 
 - `id` (String) Terraform's internal resource identifier. It is structured as "`resource_id`,`role`,`subject`".
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing project role assignment
+import {
+  to = stackit_authorization_project_role_assignment.import-example
+  id = "${var.project_id},${var.project_role_assignment_role},${var.project_role_assignment_subject}"
+}
+```

docs/resources/authorization_service_account_role_assignment.md

@@ -42,12 +42,6 @@ resource "stackit_authorization_service_account_role_assignment" "sa" {
   role        = "user"
   subject     = data.stackit_service_accounts.ske_sa_suffix.items.0.email
 }
-
-# Only use the import statement, if you want to import an existing service account assignment
-import {
-  to = stackit_authorization_service_account_assignment.sa
-  id = "${var.resource_id},${var.service_account_assignment_role},${var.service_account_assignment_subject}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -62,3 +56,17 @@ import {
 ### Read-Only
 
 - `id` (String) Terraform's internal resource identifier. It is structured as "`resource_id`,`role`,`subject`".
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing service account assignment
+import {
+  to = stackit_authorization_service_account_assignment.sa
+  id = "${var.resource_id},${var.service_account_assignment_role},${var.service_account_assignment_subject}"
+}
+```

docs/resources/cdn_custom_domain.md

@@ -25,12 +25,6 @@ resource "stackit_cdn_custom_domain" "example" {
     private_key = "-----BEGIN RSA PRIVATE KEY-----\nY2VydGlmaWNhdGVfZGF0YQ==\n-----END RSA PRIVATE KEY---"
   }
 }
-
-# Only use the import statement, if you want to import an existing cdn custom domain
-import {
-  to = stackit_cdn_custom_domain.import-example
-  id = "${var.project_id},${var.distribution_id},${var.custom_domain_name}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -63,3 +57,17 @@ Optional:
 Read-Only:
 
 - `version` (Number) A version identifier for the certificate. Required for custom certificates. The certificate will be updated if this field is changed.
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing cdn custom domain
+import {
+  to = stackit_cdn_custom_domain.import-example
+  id = "${var.project_id},${var.distribution_id},${var.custom_domain_name}"
+}
+```

docs/resources/cdn_distribution.md

@@ -116,12 +116,6 @@ resource "stackit_cdn_distribution" "example_bucket_distribution" {
     }
   }
 }
-
-# Only use the import statement, if you want to import an existing cdn distribution
-import {
-  to = stackit_cdn_distribution.import-example
-  id = "${var.project_id},${var.distribution_id}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -271,3 +265,17 @@ Read-Only:
 - `name` (String) The name of the domain
 - `status` (String) The status of the domain
 - `type` (String) The type of the domain. Each distribution has one domain of type "managed", and domains of type "custom" may be additionally created by the user
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing cdn distribution
+import {
+  to = stackit_cdn_distribution.import-example
+  id = "${var.project_id},${var.distribution_id}"
+}
+```

docs/resources/dns_record_set.md

@@ -21,12 +21,6 @@ resource "stackit_dns_record_set" "example" {
   comment    = "Example comment"
   records    = ["1.2.3.4"]
 }
-
-# Only use the import statement, if you want to import an existing dns record set
-import {
-  to = stackit_dns_record_set.import-example
-  id = "${var.project_id},${var.zone_id},${var.record_set_id}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -64,3 +58,17 @@ Optional:
 - `delete` (String) A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
 - `read` (String) A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
 - `update` (String) A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing dns record set
+import {
+  to = stackit_dns_record_set.import-example
+  id = "${var.project_id},${var.zone_id},${var.record_set_id}"
+}
+```

docs/resources/dns_zone.md

@@ -23,12 +23,6 @@ resource "stackit_dns_zone" "example" {
   description   = "Example description"
   default_ttl   = 1230
 }
-
-# Only use the import statement, if you want to import an existing dns zone
-import {
-  to = stackit_dns_zone.import-example
-  id = "${var.project_id},${var.zone_id}"
-}
 ```
 
 <!-- schema generated by tfplugindocs -->
@@ -75,3 +69,17 @@ Optional:
 - `delete` (String) A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
 - `read` (String) A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
 - `update` (String) A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
+
+## Import
+
+Import is supported using the following syntax:
+
+In Terraform v1.5.0 and later, the [` + "`" + `import` + "`" + ` block](https://developer.hashicorp.com/terraform/language/import) can be used with the ` + "`" + `id` + "`" + ` attribute, for example:
+
+```terraform
+# Only use the import statement, if you want to import an existing dns zone
+import {
+  to = stackit_dns_zone.import-example
+  id = "${var.project_id},${var.zone_id}"
+}
+```