cloudfoundry / cloudfoundry/stratos
Apply optional roles after creating org/space
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- Raised during workshop
- CLI assigns some roles after creating resources
- org - org user + org manager
- space - space manager + space developer
- Create org/space now becomes three steps
- set name & quota
- set roles
- skippable
- We should reuse the penultimate manage users step (single user selecting roles for org/space)
- async (ish) apply changes. similar to manage roles and delete app final step
- org/space create
- assign quota (think this is only at space level)
- each new org/space role
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
The issue names no files, tests, or entry points. Start by locating the org/space creation flow and the existing manage-users, manage-roles, and delete-app final-step flows. Done means optional role selection can be skipped and creation, quota, and role assignments are applied asynchronously.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100