You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Activity
ketang commentedon Jul 10, 2022
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.
ammario commentedon Jul 10, 2022
I want deprecation, but renaming seems like a good MVP solution.
ketang commentedon Jul 10, 2022
I'm okay with this as a workaround. I just wouldn't want to claim that this is the ideal way to handle deprecation.
kylecarbs commentedon Aug 24, 2022
This is done!