liquidmetal-dev / liquidmetal-dev/battery
Namespaced/multi-tenant pools
Open
Nobody has claimed this yet.
enhancement
priority/medium
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 33
Description
Scope pools and leases to a tenant/namespace and enforce isolation in the PoolAdmin/Lease API, so multiple teams or consumers can share a single poolmgrd deployment safely.
Contributor guide
No contributing guide indexed for this repository
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 tracing the PoolAdmin and Lease API entry points through poolmgrd and documenting how pools and leases are currently identified. Define the tenant/namespace isolation requirements and verify that API operations cannot cross those boundaries; done requires coverage for multiple consumers sharing one deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- authorization, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100