-
Notifications
You must be signed in to change notification settings - Fork 563
Information bubble #3887
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
Information bubble #3887
Conversation
…CloudHost, BaseObjectsSupport for users in information bubbles
migrations.RemoveField( | ||
model_name='servicebasedinformationbubble', | ||
name='groups', | ||
), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so migration 0002 is not really needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, they could've been squashed into 1. Now it's 1
I know this PR is almost finished. I'm afraid, Information Bubble is non standard and quite confusing name, isn't it ? Did we evaluate other choices ? A few options:
Alternatives
|
+1 |
Limit visibility of hosts (data center asset, virtual server, cluster, cloud host) for users in information bubble
User in an information bubble or in a group which is in an information bubble will see limited assets - asset must belong to the service env of a service which belongs to at least 1 of user's information bubble.
BaseObjectsSupport visibility is also limited (but not Support visibility as it's less clear how to do that)