Skip to content

Use stable ID in all persistent resource names #3035

Closed
@ammario

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.

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