#spacelift - February 2022

@Erik Osterman (Cloud Posse) has joined the channel

@Omry Hay has joined the channel

@kevcube has joined the channel

@Paweł Hytry - Spacelift has joined the channel

@marcinw has joined the channel

@Michael Perez has joined the channel

@Taylor has joined the channel

@Andriy Knysh (Cloud Posse) has joined the channel

@Imran Hussain has joined the channel

@RB has joined the channel

@Andy Miguel has joined the channel

@Steven Hopkins has joined the channel

@Dan Meyers has joined the channel

@johncblandii has joined the channel

@Yonatan Koren has joined the channel

@Hugo Samayoa has joined the channel

@Leo Przybylski has joined the channel

@Lucky has joined the channel

@Maxim Mironenko (Cloud Posse) has joined the channel

@Ben Smith (Cloud Posse) has joined the channel

@Jeremy G (Cloud Posse) has joined the channel

@Max Lobur has joined the channel

Spacelift has joined this channel by invitation from SweetOps.

@Jean-Marc Fontaine has joined the channel

@Kuba Martin has joined the channel

@Adam Connelly has joined the channel

@Michał Goliński has joined the channel

I'm curious what is meant by this text at the bottom of the Pulumi vendors page [1] :

Spacelift module CI/CD isn't currently available for Pulumi.

Is this referring to the terraform module dependency tracking/testing feature(s)?

[1] https://docs.spacelift.io/vendors/pulumi

Hey folks — For the spacelift-automation module — Is there a way to set global spacelift settings for a Stack? As in, if I wanted to add labels to all components in a stack is there a way to do something along the lines of the following?

settings:
  spacelift:
    labels:
      - example 

components:
  terraform:
    example1:
      vars: {}

    example2:
      vars: {}

Where both of the above components will get the example label?

@Jim Park has joined the channel

I wrote this nice pattern in our terraform-spacelift-stack module to allow creating Spacelift hooks in source repos. Maybe others will find it useful:

locals {
  base_hook_string = "if test -d .spacelift/hooks/%s ; then echo ; find .spacelift/hooks/%s -type f -executable -print | while
read -r hook ; do echo Running $hook ; $hook || exit $rc ; done ; fi"
}
resource "spacelift_stack" "this" {
  # ...
  before_init = [format(local.base_hook_string, "before_init", "before_init")]
  after_init  = [format(local.base_hook_string, "after_init", "after_init")]
  # etc
}

Then you can add hooks as executable files in your source repo to $project_root/.spacelift/after_apply/ 🙌

Best Infrastructure as Code Tools (IaC) for DevOps
More and more Engineering organizations are moving towards Infrastructure as Code (IaC). See our article and find out the best IaC tools avaliable for your DevOps team.

I had a terraform destroy spacelift task fail because it was trying to destroy a backup vault that still had recovery points in it. I manually deleted the recovery points and then attempted to run destroy again. Unfortunately, I'm getting the error :

│ Error: Can't ask approval for state migration when interactive input is disabled.
│ 
│ Please remove the "-input=false" option and try again.

Any ideas how to fix this?

Hi. I'm fairly new to Spacelift, trying it out as a replacement for TF Cloud for our business. I was wondering if anybody here has used stacks with AWS integration using public workers. The thing I'm trying to wrap my head around is how to go about doing a PR, that requires a terraform import as part of the release. Usually with TF Cloud, I had a backend configuration in my .tf files, and I would do a terraform import locally (with the remote state), then merge the PR. With Spacelift, how do you deal with PRs that would require an import as part of the release? There seems to be no documentation I can find around this process.

Terraform Locals – How to Use Them (Examples)
Terraform local variables. Learn what are they and how to use Terraform locals. See examples.

Terraform Count and For_Each Meta-Argument Overview
See how and when to use Terraform count and for_each. Learn things to keep in mind when working with these Terraform meta-arguments.

Ansible Tutorial for Beginners: Installation, Playbook, Examples
What is Ansible? How does it work? See the Ansible tutorial for beginners with playbook and commands explained with examples.

Can someone point me to the docs on importing existing Spacelift stacks into Terraform?

Is there a way to see the config for each run? Specifically, I’m thinking about the environment, but full context for the run would be very nice.

Is there a way to use Spacelift-managed state from outside Spacelift? I think not...

Is there a difference between the TRIGGER button on the stack pages and the RETRY button on the run pages?

Say, for example, I changed the base_dir between runs. Is there a difference in what is triggered by those two buttons? Would RETRY possibly still use the base_dir from the run it’s retrying, instead of the newly-updated value? or any other settings…