In an effort to automate in-repo Spacelift stacks, I hope to run the spacelift module after terraform adds the new repo to the Spacelift’s Github App installation of allowed repos. When setting module.spacelift to depend_on the github_app_installation_repositories resource, I’m getting an error that seems to originate within the CloudPosse Spacelift Module (in 🧵 ).
Any suggestions on only executing cloudposse/cloud-infrastructure-automation/spacelift after another resource completes?
D
dudealmost 3 years ago
@dude has joined the channel
Erik Osterman (Cloud Posse)almost 3 years ago
Thoughts on splitting this channel into spacelift-announcements and spacelift? The blog posts drownout any conversation.
We’re starting to finally do drift detection with Spacelift, just using the default built-in drift detection they offer on private workers. I was curious if any of you use different drift detection tools with Spacelift, and if so, if those tools support provider aliasing and multi-account/region stacks.
