digitalocean / digitalocean/omniauth-digitalocean
Access only to specific resources
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 33
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
is it possible to use DigitalOcean oauth (e.g. this official gem) to grant access only to specific resources (and not to the entire account)?
For example, think about a CI/CD service that needs to deploy to a Kubernetes cluster hosted on Digitalocean: how can it access ONLY to it? What do you recommend?
It might appear scary for the user to grant access to the whole account.
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 reviewing the official DigitalOcean OAuth gem and the repository's OAuth strategy entry point to determine whether resource-level access scopes are supported. Done means establishing whether CI/CD access can be limited to one Kubernetes cluster and documenting the supported model or the limitation; the issue names no tests or files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100