Skip to main content

Updates

Follow new updates and improvements to Spacelift.

OpenTofu is now GA!!!

OpenTofu is growing up fast and we are proud to be one of the founding members of this initiative. Apart from supporting OpenTofu natively as part of the platform, we offer native and commercial support to ensure your OpenTofu workflows run smoothly.Read more about the release here and find out more details about it.

Announcement

Enabling git checkout support for GitHub

Over the past week, Spacelift customers have been impacted by various GitHub incidents that have resulted in Spacelift not being able to download the source code for stacks and modules. Although these incidents are not directly related to any changes within Spacelift, this is causing Spacelift customers to experience intermittent issues executing runs and deploying new module versions, and we have been investigating what we can do to mitigate the problems.
We have raised a support issue with GitHub to try to work with them to resolve the problems, but in the meantime we want to provide a potential fix for customers who are experiencing issues.
Currently Spacelift uses the GitHub API to download the source code for stacks/modules as a tarball, but we have introduced experimental support for using standard Git cloning instead. We are initially introducing this on an opt-in basis so that affected customers can decide on a case-by-case basis whether to enable the feature. We believe that this may be a viable approach because based on our observations and customer feedback, core git functionality in GitHub does not appear to be impacted as much as downloading code via the API.
What do I need to do to enable the feature?
  1. To enable the feature for a single stack or module, just add the feature:enable_git_checkout label to it.
  2. If you would like to have the feature enabled globally for your account, please message us on Slack and we will do so.
Next steps
Initially we want to provide this functionality on an opt-in basis, but assuming it's working well, we will roll it out to all customers. We will provide a further update before that process begins.

Learn more in our documentation

Announcement

Clarification of Policy Backwards-Compatiblity

Hey!

We’ve clarified in our documentation our approach to policy backwards-compatibility.

With this in mind, we’ll be introducing a new feature soon (18th September) - approval policy evaluation for proposed runs whose plan policies signal a warning. Proposed runs that result in a plan policy warning will now go into the PENDING_REVIEW state if there is any approval policy attached, and wait in this state for approval. This will let you set up flows where proposed runs will only be marked as successfully finished (and e.g. unblock related pull requests) when all interested stakeholders have signed off on them.

This means that you should make sure your approval policies are able to handle such a new state, as is shown in the new documentation section.

Learn more in our documentation

Announcement

Earlier updates