From d7337d9c4e7a576992f6c790b24bc8b0c07f6565 Mon Sep 17 00:00:00 2001 From: Viktor Trykolenko <1419684+victr@users.noreply.github.com> Date: Fri, 15 Nov 2024 13:46:45 +0100 Subject: [PATCH 1/2] Fix a typo in state-management.md --- docs/vendors/terraform/state-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/vendors/terraform/state-management.md b/docs/vendors/terraform/state-management.md index de6b991cc..4bf88f0f1 100644 --- a/docs/vendors/terraform/state-management.md +++ b/docs/vendors/terraform/state-management.md @@ -45,8 +45,8 @@ root of your Terraform project as a `.tf` file. If you have some Terraform state backend already specified in your code, the initialization phase will keep failing until you remove it. The state server is an HTTP endpoint implementing the -Terraform [standard state management protocol](https://www.terraform.io/docs/backends/types/http.html){: rel=" -nofollow"}. Our backend always ensures that the credentials belong to one of the runs or tasks that are currently marked +Terraform [standard state management protocol](https://www.terraform.io/docs/backends/types/http.html){: rel="nofollow"}. +Our backend always ensures that the credentials belong to one of the runs or tasks that are currently marked as active on our end, and their state indicates that they should be accessing or modifying the state. Once this is established, we just pass the request to S3 with the right parameters. From 1d28f7d3f8cb20a795e8785662c8ea2d9ec7acd5 Mon Sep 17 00:00:00 2001 From: Viktor Trykolenko <1419684+victr@users.noreply.github.com> Date: Fri, 15 Nov 2024 13:54:56 +0100 Subject: [PATCH 2/2] Fix lint and another typo --- docs/vendors/terraform/state-management.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/vendors/terraform/state-management.md b/docs/vendors/terraform/state-management.md index 4bf88f0f1..0c237794a 100644 --- a/docs/vendors/terraform/state-management.md +++ b/docs/vendors/terraform/state-management.md @@ -45,7 +45,7 @@ root of your Terraform project as a `.tf` file. If you have some Terraform state backend already specified in your code, the initialization phase will keep failing until you remove it. The state server is an HTTP endpoint implementing the -Terraform [standard state management protocol](https://www.terraform.io/docs/backends/types/http.html){: rel="nofollow"}. +Terraform [standard state management protocol](https://www.terraform.io/docs/backends/types/http.html){: rel="nofollow"}. Our backend always ensures that the credentials belong to one of the runs or tasks that are currently marked as active on our end, and their state indicates that they should be accessing or modifying the state. Once this is established, we just pass the request to S3 with the right parameters. @@ -103,8 +103,8 @@ After rollback completes successfully, a new version of your state will appear a ## Importing resources into your Terraform State So you have an existing resource that was created by other means and would like that resource to be reflected in your -terraform state. This is an excellent use case for the [terraform import](https://www.terraform.io/cli/import){: rel=" -nofollow"} command. When you're managing your own terraform state, you would typically run this command locally to +terraform state. This is an excellent use case for the [terraform import](https://www.terraform.io/cli/import){: rel="nofollow"} +command. When you're managing your own terraform state, you would typically run this command locally to import said resource(s) to your state file, but what do I do when I'm using Spacelift-managed state you might ask? Spacelift [Task](../../concepts/run/task.md) to the rescue!