Skip to main content

Stack IDs should be a unique ID, not the name of the stack

Feature Requests

Right now during stack creation the ID generated for it (stack slug) is the name of the stack.

When the stack is renamed, the ID is not changed and can cause confusing situations when for example using the CLI.

Ideally, the stack ID is a unique ID and unrelated to the stack name.

Workaround
Status: ⬆️ Gathering votes3 comments

This request was merged into another request

Comments3

  • Rose Beaver

    •

    Jan 21

    I have struggled with slugs a few times. First they need to be account-unique, not space-unique, second they cannot be changed easily and finally they are used in GHA naming…

    In a way, the AWS-style IDs really work well in this regards: stack-<UNIQUE_ID>, although, not perfectly human-readable.

  • Rose Newt

    •

    Nov 25, 2024

    I wish to second this. Provisioning spacelift via TF provider and providing the ID’s would make provisioning and management so much easier. Currently we have automation asking the users for a space name they want, but when the automation creates it, its ID is autogenerated. This makes later automation to remove or archive the spaces difficult, as we dont want to then store that ID elsewhere so that users can request it removed when required.

  • Natalia Gazda

    Team•

    Oct 30, 2024

    @Joost Polley thanks for the request! We evaluated it, and we understand the point and thinks there is sense in doing that, however it would not be a top priority for us now. Switching to autogenerated IDs would require ongoing support for two types of IDs, making it a longer-term project. I’ll leave it in “Gathering Votes” and we’ll revisit it next year.