Public bug reported:
Disabling and deleting currently-logged-in project and domain need to be
handled with same method.
Stricktly speaking, we should use the same policy for the following actions:
- Disable current project
- Delete current project
- Disable current domain
- Delete current domain
----
To handle the above actions, two different strategies exist:
1- Disallow users to do the action
2- Allow to do, but handle the error
----
Current status of the aboved mentioned actions is as follows:
- Disable current project(Disallowed)
--->https://review.openstack.org/#/c/138383/
- Delete current project(Allowed) --->https://review.openstack.org/#/c/199410/
- Disable current domain(Allowed) ---> (I reported the bug:
https://bugs.launchpad.net/horizon/+bug/1494448)
- Delete current domain(Allowed but if domain is disabled)
---
Using the same method for all of the above actions is what we should do to
avoid inconsistency in Horizon UI.
** Affects: horizon
Importance: Undecided
Assignee: hossein zabolzadeh (zabolzadeh)
Status: New
** Changed in: horizon
Assignee: (unassigned) => hossein zabolzadeh (zabolzadeh)
** Description changed:
Disabling and deleting currently-logged-in project and domain need to be
handled with same method.
Stricktly speaking, we should use the same policy for the following actions:
- Disable current project
- Delete current project
- Disable current domain
- Delete current domain
----
To handle the above actions, two different strategies exist:
1- Disallow users to do the action
2- Allow to do, but handle the error
----
Current status of the aboved mentioned actions is as follows:
- Disable current project(Disallowed)
--->https://review.openstack.org/#/c/138383/
- Delete current project(Allowed) --->https://review.openstack.org/#/c/199410/
- - Disable current domain(Allowed)
+ - Disable current domain(Allowed) ---> (I reported the bug:
https://bugs.launchpad.net/horizon/+bug/1494448)
- Delete current domain(Allowed but if domain is disabled)
- ---
+ ---
Using the same method for all of the above actions is what we should do to
avoid inconsistency in Horizon UI.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1494464
Title:
use-same-method-to-handle-delete-current-project-and-domain
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Disabling and deleting currently-logged-in project and domain need to be
handled with same method.
Stricktly speaking, we should use the same policy for the following actions:
- Disable current project
- Delete current project
- Disable current domain
- Delete current domain
----
To handle the above actions, two different strategies exist:
1- Disallow users to do the action
2- Allow to do, but handle the error
----
Current status of the aboved mentioned actions is as follows:
- Disable current project(Disallowed)
--->https://review.openstack.org/#/c/138383/
- Delete current project(Allowed) --->https://review.openstack.org/#/c/199410/
- Disable current domain(Allowed) ---> (I reported the bug:
https://bugs.launchpad.net/horizon/+bug/1494448)
- Delete current domain(Allowed but if domain is disabled)
---
Using the same method for all of the above actions is what we should do to
avoid inconsistency in Horizon UI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1494464/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
