Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Add check for both workspace and multi tenancy enabled #1819

Open
Hailong-am opened this issue Mar 8, 2024 · 4 comments
Open

[FEATURE] Add check for both workspace and multi tenancy enabled #1819

Hailong-am opened this issue Mar 8, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request triaged

Comments

@Hailong-am
Copy link
Contributor

Is your feature request related to a problem?

The workspace feature will have similar functionality with multi tenancy. If they are both turned on that may confuse user, as there have two ways to separated data.

What solution would you like?

Add a check in security dashboard plugin to check if workspace plugin is turned on and multi tenancy is on, then OSD will exit and print out an error message when startup.

The reason why not add this check in workspace plugin are

  1. Workspace can't depends on security dashboard plugin as the code are sit in OSD repo
  2. No way for workspace plugin read the config of security dashboard plugin, as plugins are not allowed to read config of other plugins.

What alternatives have you considered?

Do you have any additional context?
opensearch-project/OpenSearch-Dashboards#4944

@Hailong-am Hailong-am added enhancement New feature or request untriaged labels Mar 8, 2024
@Hailong-am
Copy link
Contributor Author

this can assign to me, i will add the check

@peternied
Copy link
Member

The workspace feature will have similar functionality with multi tenancy. If they are both turned on that may confuse user, as there have two ways to separated data.

@Hailong-am could you please describe the scenarios that will be confusing? For customers that are already using multi tenancy this will also be confusion. I suspect the UX will need changes to help mitigate this confusion, what do you think?

@Hailong-am
Copy link
Contributor Author

could you please describe the scenarios that will be confusing?

If a user create a few different workspaces with dashboards, those dashboards will be isolated by workspace. They can switch between workspaces like switch tenancy. However, with workspace mixed with tenancy, user need to pay attention to two things, workspace and tenancy. A user create a workspace and that will store in .kibana index by default, then it switch to another tenancy, all those data are missing. they may wonder where is my workspace.

For customers that are already using multi tenancy this will also be confusion.

If they want to give a try to workspace, they could turn off mutli tenancy for a while and change it back when finshed.

I suspect the UX will need changes to help mitigate this confusion, what do you think?

Yes, that will have tenancy migration guide when start to use workspace at the first time.

@stephen-crawford
Copy link
Contributor

[Triage] Hi @Hailong-am thanks for filing this issue. This seems like we can move forward with the change you suggested. I will also go ahead and assign this to you like you asked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triaged
Projects
None yet
Development

No branches or pull requests

3 participants