Geoelycom · Geoelycom · May 2, 2025 · May 1, 2025
diff --git a/terraform_imports/.terraform.lock.hcl b/terraform_imports/.terraform.lock.hcl
diff --git a/terraform_imports/docker.tf b/terraform_imports/docker.tf
@@ -0,0 +1,19 @@
+# Terraform configuration
+# Configuration-driven import relies on the import block, which has two required arguments:
+
+# - resource_type: The type of resource to import, in this case, docker_container.
+# - resource_name: The name of the resource to import, in this case, my_container.
+
+import {
+  id = "305226eb8001ec8363cf1c2500b63566651362a7dbd45ada90b7163e33d8d215"
+  to = docker_container.web
+}
+
+# generating configuration with the cli is better than manually defining the resources  by using
+# terraform plan -generate-config-out=generated.tf flag.
+
+# The import block is used to import existing resources into Terraform state. The id argument specifies the ID of the resource to import, and the to argument specifies the name of the resource in the Terraform configuration.
+
+resource "docker_image" "nginx" {
+  name = "nginx:latest"
+}
diff --git a/terraform_imports/generated.tf b/terraform_imports/generated.tf
@@ -0,0 +1,26 @@
+# __generated__ by Terraform
+# Please review these resources and move them into your main configuration files.
+
+# __generated__ by Terraform from "305226eb8001ec8363cf1c2500b63566651362a7dbd45ada90b7163e33d8d215"
+resource "docker_container" "web" {
+  env   = []
+  image = docker_image.nginx.image_id
+  name  = "hashicorp-import"
+  ports {
+    external = 8081
+    internal = 80
+    ip       = "0.0.0.0"
+    protocol = "tcp"
+  }
+}
+
+# its possible to bring some resources under terraform management by using the terraform import command. this is often the case for resources defined by a single unique ID or Tag, such as Docker images
+
+# terraform import docker_container.web 305226eb8001ec8363cf1c2500b63566651362a7dbd45ada90b7163e33d8d215
+
+# In the above generated.tf file, the docker_container.web resource specifies the SHA256 hash ID of the image used to create the container. This is how Docker stores the image ID internally, so the import operation loaded the image ID directly into your state. However, identifying the image by its tag or name would make your configuration easier to understand.
+# but we can make it easily readable by using the image name instead of the sha256 hash. To do this, we can use the docker_image data source to look up the image by its name and tag. The data source will return the SHA256 hash ID of the image, which we can then use in our docker_container resource.
+# we retrieve it with the following command: 
+# docker image inspect -f {{.RepoTags}} `docker inspect --format="{{.Image}}" hashicorp-import`
+
+# include it into the resources block : name: "nginx:latest"
diff --git a/terraform_imports/main.tf b/terraform_imports/main.tf
@@ -0,0 +1,3 @@
+provider "docker" {
+
+}
diff --git a/terraform_imports/terraform.tf b/terraform_imports/terraform.tf
@@ -0,0 +1,19 @@
+terraform {
+  /* Uncomment this block to use Terraform Cloud for this tutorial
+  cloud {
+      organization = "organization-name"
+      workspaces {
+        name = "learn-terraform-import"
+      }
+  }
+  */
+
+  required_providers {
+    docker = {
+      source  = "kreuzwerker/docker"
+      version = "~> 3.0.2"
+    }
+  }
+
+  required_version = "~> 1.5"
+}