Troubleshooting Module Version Not Being Created in Spacelift

Last updated: November 10, 2024

Issue: New Module Version Not Created

If a new module version isn’t appearing as expected, there are several common reasons. This guide outlines the usual causes and provides steps to help you diagnose and resolve the issue.

Common Reasons for Missing Module Versions

  1. Version Already Exists
    If the version you’re trying to create is already in the registry, Spacelift will not create a duplicate. Verify that the version is unique and hasn’t been previously registered.

  2. Push Policy Preventing Version Creation
    Check if there is a Push policy attached to your module that might be blocking version creation. Push policies can include conditions or filters that restrict version creation under certain circumstances.

  3. Configuration File Misnamed
    The module configuration file must be named config.yml (not config.yaml). A misnamed file can prevent Spacelift from recognizing the module configuration and creating new versions.

Next Steps

If none of the above reasons apply, please reach out to our support team with the commit SHA of the push for the module, and our team will investigate further.