From 562ce346c77eddd8b0fa981ecc086c40ffd0e618 Mon Sep 17 00:00:00 2001 From: Andrew N Golovkov <147300+Andor@users.noreply.github.com> Date: Wed, 21 Feb 2024 16:13:23 +0200 Subject: [PATCH] docs(importing-resources): fix wording (#1607) --- docs/guides/importing-resources.md | 4 ++-- templates/guides/importing-resources.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/guides/importing-resources.md b/docs/guides/importing-resources.md index a2c93dc1f..3a2753351 100644 --- a/docs/guides/importing-resources.md +++ b/docs/guides/importing-resources.md @@ -5,7 +5,7 @@ page_title: "Importing existing Aiven infrastructure" # Importing existing Aiven infrastructure If you have already manually created an Aiven environment, it is possible to import all resources and start managing them with Terraform. -The ID format for each resource but typically it is `/` for resources that are directly under project level and `//` for resources that belong to specific service. +The ID format typically is `/` for resources that are directly under project level and `//` for resources that belong to specific service. As example, to import a database called `mydb` belonging to the service `myservice` in the project `myproject`, you can run: ```bash @@ -15,4 +15,4 @@ $ terraform import aiven_database.mydb myproject/myservice/mydb In some cases the internal identifiers are not shown in the Aiven web console. In such cases the easiest way to obtain identifiers is typically to check network requests and responses with your browser's debugging tools, as the raw responses do contain the IDs. ## Using data sources -Alternatively you can define already existing, or externally created and managed, resources as [data sources](../data-sources). \ No newline at end of file +Alternatively you can define already existing, or externally created and managed, resources as [data sources](../data-sources). diff --git a/templates/guides/importing-resources.md b/templates/guides/importing-resources.md index a2c93dc1f..3a2753351 100644 --- a/templates/guides/importing-resources.md +++ b/templates/guides/importing-resources.md @@ -5,7 +5,7 @@ page_title: "Importing existing Aiven infrastructure" # Importing existing Aiven infrastructure If you have already manually created an Aiven environment, it is possible to import all resources and start managing them with Terraform. -The ID format for each resource but typically it is `/` for resources that are directly under project level and `//` for resources that belong to specific service. +The ID format typically is `/` for resources that are directly under project level and `//` for resources that belong to specific service. As example, to import a database called `mydb` belonging to the service `myservice` in the project `myproject`, you can run: ```bash @@ -15,4 +15,4 @@ $ terraform import aiven_database.mydb myproject/myservice/mydb In some cases the internal identifiers are not shown in the Aiven web console. In such cases the easiest way to obtain identifiers is typically to check network requests and responses with your browser's debugging tools, as the raw responses do contain the IDs. ## Using data sources -Alternatively you can define already existing, or externally created and managed, resources as [data sources](../data-sources). \ No newline at end of file +Alternatively you can define already existing, or externally created and managed, resources as [data sources](../data-sources).