Skip to content

Allow renaming templates #2877

Closed
Closed

Description

@ammario

As a template admin, I want to efficiently inform my users that a template is deprecated. My preferred method of doing so would be to rename a template to <oldname>-deprecated. The user would likely explore the template README for the correct template.

Activity

  1. ketang commented on Jul 10, 2022

    @ketang
    Contributor

    Do you want renaming or do you want deprecation? We should have renaming for its own sake. Deprecation... perhaps we can handle that as a first class concept to go with our template update lifecycle. It would prevent new workspaces from being created with that template but allow restarts of existing ones.

  2. ammario commented on Jul 10, 2022

    @ammario
    MemberAuthor

    I want deprecation, but renaming seems like a good MVP solution.

  3. ketang commented on Jul 10, 2022

    @ketang
    Contributor

    I'm okay with this as a workaround. I just wouldn't want to claim that this is the ideal way to handle deprecation.

  4. kylecarbs commented on Aug 24, 2022

    @kylecarbs
    Member

    This is done!

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