cloudfoundry / cloudfoundry/stratos
Handle suspended orgs in permission model
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
Check the CF Api docs.
- User shouldn't be able to push applications to it.
- Create Space should be hidden an org is suspended.
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 with the Cloud Foundry API documentation and the permission model entry points. Trace how suspended organizations are represented and how application pushes and Create Space visibility are authorized. Done means suspended organizations cannot receive application pushes and do not show Create Space.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- authorization, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100