cloudfoundry / cloudfoundry/stratos
Improve bulk changes of cf user roles
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
We can now manage user/s roles (see #2118). However, the process could be improved when changing many roles.
At the point where we make the changes we display a table with rows per change. The right most column shows the status of the change (in progress/success/failed - see #2124 for work to tie in failure message). At the moment there's no indication when all changes have completed (successfully/partially) and the performance can suffer (stuttering updates). Need to...
- Understand what the reasonable upper limit of role changes should be (20, 50, 100, 500?)
- Ensure we don't spam the backend by batching requests?
- Show a global status for all requests in the generic monitor action table?
- Understand the effect of redux dev tools in performance of page
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the user-role changes from #2118, the generic monitor action table, and the failure-message work in #2124. Investigate how many role changes can be handled, whether requests should be batched, how to show an overall completion status, and the performance effect of Redux DevTools. Done means these questions have a decided implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, redux, typescript
- Domain
- authorization, frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100