Hi all, that's my first contact, happy to get in t...
# atmos
m
Hi all, that's my first contact, happy to get in touch with you 🙂 I am doing a PoC with atmos and spacelift.io. I read about the integration between atmos and spacelift and tried to follow the docs. I was able to create spacelift spaces and stacks with your provided TF modules: https://github.com/cloudposse-terraform-components/aws-spacelift-admin-stack and https://github.com/cloudposse-terraform-components/aws-spacelift-spaces. But now I am blocked to follow the documentation because it mentions the below scripts to be used in the spacelift stack hooks. For example:
Copy code
before_init:
  - spacelift-configure-paths
  - spacelift-write-vars
  - spacelift-tf-workspace
Example copied from https://github.com/cloudposse-terraform-components/aws-spacelift-admin-stack?tab=readme-ov-file#usage Obviously these scripts do not exist in the default spacelift runner image and the stack run fails. Just commenting them out makes the default OpenTofu workflow fail. I searched for hours but I was not able to find examples or more information about these scripts. Maybe someone can point me into the right direction and help me to find these scripts? Thanks a lot 🙂
e
Good to have you hear, and have some good news / bad news.
We will not continue to invest our spacelift modules due to our investment in native CI with atmos, GitHub actions, and our operational control plane atmos-pro.com
Spacelift is a great platform and they are amazing stewards of OpenTofu. We have a different roadmap that didn't align with theirs.
The good news is that if you are looking for a control plane, atmos-pro.com is much easier to setup and faster to operate in large environments
Its not required though, and native CI support with GitHub actions is entirely free
m
Hey! We might be able to help cause we're currently leveraging this functionality. Mind if I reach out @Martin Bornhold?
👍 1