[FEATURE] Fine grained access control - agroup can be a reader for one config & contributor for another config
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 396
- Forks
- 83
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
We cannot assign groups permissions in such a way that the group can have Viewer access in Production environment/configuration and Contributor access for the rest of the configurations
Describe the solution you'd like
Implement fine grained controls in such a way that a group can be Viewer only in a particular environment/configuration and can be Collaborator for other configurations.
Describe alternatives you've considered
No alternative is possible at this time.
Additional context
We are trying to assign permissions through Terraform.
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
The issue names no files, tests, or entry points, so begin by locating the CLI's permission-related code and its Terraform integration. Done means a group can be Viewer in one specified environment or configuration while remaining Collaborator for other configurations, with the behavior verifiable through Terraform.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, terraform
- Domain
- authorization, cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100