Skip to content

Use stable ID in all persistent resource names #3035

Closed

Description

@ammario

As we add workspace renaming (#3000) and username renaming, it's possible that a persistent resource has a name that is misaligned with the workspace name. Not only is this confusing, it can lead to naming conflicts and messy states.

We should change our example templates and documentation to use ID everywhere.

Activity

  1. kylecarbs commented on Aug 24, 2022

    @kylecarbs
    Member

    #3663 mostly does this. We could remove the dynamic vals from the Terraform provider, but that seems weird.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions