Skip to main content

Do not allow stack to deploy from an archived gitlab repo

Feature RequestsIaC WorkflowsSelf-hosted

I would like to have the option to disable spacelift from being able to deploy from an archived gitlab repo.

During our decomissioning process there can be situations where a stack exists, its resources have been destroyed and the gitlab repo has been archived. If left in this state the spacelift stack can be re-ran and would read from the archived repo which is undesirable

Status: ❌ Rejected2 comments

Log in to comment and vote

Comments2

  • Black Breeze

    •

    Feb 9

    Thanks for the detailed feedback about your decommissioning workflow. I understand the concern about preventing accidental deployments from archived repositories.

    While we see how this would help your specific workflow, this feels like something better solved at the process level rather than in Spacelift. Here are a couple of approaches that would address your safety concern:

    • Delete the stack during decommissioning: When you destroy resources and archive the repo, also delete the corresponding Spacelift stack. This eliminates any possibility of accidental re-runs.

    • Disable the stack before archiving: You can manually disable the stack in Spacelift settings before archiving the GitLab repo. Disabled stacks won't respond to any triggers.

    • Use stack locking: During your decommissioning process, lock the stack to prevent any runs until you're ready to delete it.

    These approaches give you the same safety guarantee without requiring Spacelift to monitor repository archive status.

    • Teal Mongoose

      •

      Feb 9

      Thanks for the quick response and recommendations!