cloudfoundry / cloudfoundry/stratos
Cater for Organisation Auditor + Billing Manager
Open
Nobody has claimed this yet.
community
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- Create/Edit/Delete actions respect all roles + their permissions
- View permissions are normally left to cf and whatever it returns upon request (user cannot view certain space so it's omitted from result)
- There are some cases where no entities will ever be returned, and we shouldn't show lists or sections of the console
- Org Auditors and billing manager do not have rights to view spaces or app details. We shouldn't show stats that are made up from spaces or their apps, spaces tabs, app details, etc
- This will effect a fair amount and is not something we cater for in v1 at the moment, therefore is not included in #2175
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
Review issue #2175 and the console's existing role and permission handling first. Trace how Org Auditor and Billing Manager access is represented, then verify that inaccessible spaces and app-derived statistics, tabs, details, lists, and sections are omitted; the issue names no files or tests, so the relevant entry points must be located in the console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- authorization, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100