State management
Last updated
Was this helpful?
Last updated
Was this helpful?
For those of you who don't want to manage Terraform state, Spacelift offers an optional sophisticated state backend synchronized with the rest of the application to maximize security and convenience. The ability to have Spacelift manage the state for you is only available during .
As you can see, it's also possible to import an existing Terraform state at this point, which is useful for users who want to upgrade their previous Terraform workflow.
In this section we'd like to give you a few reasons why it could be useful to trust Spacelift to take care of your Terraform state. To keep things level, we'll also give you a few reasons not to.
It's super simple - just two clicks during stack setup. Otherwise there's nothing to set up on your end, so one fewer sensitive thing to worry about. Feel free to refer to , but overall we believe it to be a rather sensible and secure setup, at least on par with anything you could set up on your end.
It's protected against accidental or malicious access. Again, you can refer to the more technical section on the inner workings of the state server, but the gist is that we're able to map state access and state changes to legitimate Spacelift runs, thus automatically blocking all other unauthorized traffic. As far as we know, no other backend is capable of that, which is one more reason to give us a go.
Unless you explicitly export it using a Spacelift , the state can't be accessed outside authorized and . In particular, this makes sharing the state between stacks impossible using the Terraform mechanism of . This is by design, and we believe that remote state is usually an anti-pattern, but hey, anti-patterns are sometimes super useful too. We offer an attractive alternative with but if you can't avoid accessing remote state, you're better off managing the state on your end.
We'll let you in on a little secret now - behind the pixie dust it's still S3 all the way down, and at this stage . If you're not OK with that, you're better off managing the state on your end.
If you want to frequently access your state offline for analytical or compliance purposes and aren't happy doing it using Spacelift (BTW, let us know why) then again you're better off managing the state on your end.
S3, like half of the Internet. The pixie dust we're adding on top of it involves generating one-off credentials for every and and injecting them directly into the 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.
To do this, use the following steps:
Select the Spacelift Stack to which you would like to import state for.
Within the navigation, select "Tasks"
Run the terraform import command needed to import your state file to the Spacelift-managed state by typing the command into the text input and clicking the perform button. Note: If you are using Terragrunt on Spacelift, you will need to run terragrunt import
Follow the status of your task's execution to ensure it was executed successfully. When completed, you should see an output similar to the following within the "Performing" step of your task.
The state server is an HTTP endpoint implementing the Terraform . 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.
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 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 to the rescue!
