Custom Scopes for Key-Value Store + RBAC for that Scopes
Open
Nobody has claimed this yet.
feature
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
Hi Community,
Than a Company have different Teams that shares a st2 instance it would be nice if any Team could create there own scope. So all Team Members of Team1 can see all Key/Values of Team1 and all Team2 Members can se all key Values of Team 2. But Team 1 can not access Team2 and Team 2 can not access Team1 keys.
- Have Custom Scopes.
- Allow set a rbac rule on Scope.
- Allow a Setup in Rule to set the Scope for KV that shoud use by System for that Rule.
What do you think about that Idea?
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. Begin by locating StackStorm's key-value store and RBAC implementations, then clarify the scope model, rule configuration, isolation behavior, and acceptance tests with maintainers before attempting work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100