Deprecate namespace strategies other than "per user" #19365
Labels
area/che-server
kind/task
Internal things, technical debt, and to-do tasks to be performed.
new¬eworthy
For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
Milestone
Is your task related to a problem? Please describe.
When switching to DevWorkspace we would like to drop support for namespace strategies other than "per user".
One and only one namespace per user simplifies a lot the design of the workspaces.
We could assume then that every user configuration lives in his namespace.
Describe the solution you'd like
At the "deprecation" stage we need to reflect that fact on documentation and add a warning when someone wants to use it.
Describe alternatives you've considered
Remove support without "deprecation" stage
Additional context
n/a
The text was updated successfully, but these errors were encountered: