Skip to main content

Migrating and Reparenting Stacks Between Spaces While Preserving Run History

Feature Requests

There is a need to migrate and reparent stacks between spaces while preserving the run history. Currently, moving stacks between spaces can result in loss of execution history, which makes it difficult to track the progress and state of stacks over time.

The goal is to use the Spacelift API to facilitate this operation, ensuring that when a stack is moved from one space to another, its run history remains intact. This is important for maintaining visibility and continuity across environments, as it allows users to reorganize their infrastructure without losing valuable context on the stack’s performance.

Status: 🗑️ Archived2 comments

Log in to comment and vote

Comments2

  • Black Breeze

    •

    Jun 10, 2025

    Hey Trevor - what you’re describing is not the expected product behavior, and moving stacks between spaces should not result in history loss. I escalated this to solutions engineering and someone will be reaching out to you to verify what I see essentially as a bug report.

    If there’s indeed a bug, we will address it through our Engineering escalation channels.

    • Yellow Mirror

      •

      Jun 23, 2025

      Not a bug per se but more of a usability improvement. Recently went through a large stack reorganization and the stack names (slug) encode part of the ownership hierarchy. Just wanted to be able to rename / reslug the stacks simply. Renaming the stack via the UI does not change the slug (by design) since this is a globally unique ID. We were able to accomplish what we needed using an unpublished API to reslug.