UI flow: have Collector generate collector credentials, provide them to Divvi Up
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
An idea from today's planning meeting: today, we will expect users to generate their collector credentials via a CLI tool. Another approach that would work would be to expect the Collector to generate & store these credentials, and use Divvi Up's API to communicate these credentials.
Some thoughts:
- Initial implementation could be by the already-existing API tokens -- this would work today, but requires the person configuring the Collector to provide this one token. An easier flow may be possible via OAuth, but this would require implementation work.
- Ideally, this would be something we could document well enough that non-DU-authored Collectors could use the flow, too.
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 existing CLI-based credential flow, the Collector, and the Divvi Up API, including the current API-token approach. Decide whether the first implementation should use API tokens or OAuth, then define the credential generation, storage, communication, and documentation flow for non-DU-authored Collectors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authentication, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100