Bug 1618644
| Summary: | Switch menu items by user role | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Takayuki Konishi <tkonishi> | ||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 3.10.0 | CC: | aos-bugs, deads, jokerman, mhild, mmccomas | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-06-04 20:34:13 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Takayuki Konishi
2018-08-17 08:06:50 UTC
I agree this isn't an ideal experience. Unfortunately this is a limitation in the console because there is no API we can use to easily check. It requires a separate request for every project, which is prohibitively expensive if you have a large number projects in the list. I disagree. You could make the request to check if the project is deletable with your account when showing the "delete modal". See attachment. Going further you could work with the API team to annotate the "list projects" call with that information. Created attachment 1477125 [details]
delete modal
(In reply to Marcel Hild from comment #2) > Going further you could work with the API team to annotate the "list > projects" call with that information. I expect that would be very expensive to do. David? Annotating a project with "can you delete this information"? It goes against several api conventions. 1. all viewers of a resource see the same resource 2. a round-trip (read/write) cycle doesn't change content 3. no "special" fields for server mechanics We can't pursue that path. This will be addressed in the 4.2 console where we perform a SelfSubjectAccessReview when the user opens the kebab menu [1]. We do not plan to address this in the 3.x console. [1] https://github.com/openshift/console/pull/1559 |