zalando / zalando/postgres-operator
Utilizing the Teams API for basic Permissions (e.g. `view`, `writer` or `admin`)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
- Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS K8s
- Are you running Postgres Operator in production? no
- Type of issue? question / feature
I was wondering if it's possible to utilize the Teams API (or somehow using the operator) to not only grant "admin" permissions on the databases, but somehow be able to say this database is owned by team x => they would get admin permissions, however, team y would only get view permissions.
Using the CRD PostgresTeam and adding team y as an additional team would grant team y also admin permissions which is something I am not after ..
Would something like that be possible?
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 by reviewing the PostgresTeam CRD and the operator's Teams API permission handling. Determine whether separate view, writer, and admin access can be represented for teams, and consider the work complete when a database can assign distinct permissions to different teams.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- authorization, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100