spinframework / spinframework/spin
Move Redis trigger implementation to separate repo
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
As discussed in this PR #1717, this issue proposes to move the Redis trigger implementation out of the core Spin repo, and to it's own repository, making it a plugin.
The main reason behind this is to make the core Spin repository more lean in it's feature set, and set a precedence for triggers, other than https, to be plugins to the core runtime.
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
Read PR #1717 first, then locate the Redis trigger implementation in the core Spin repository. Define the separate plugin repository boundary and verify that the core repository no longer owns the Redis trigger.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, rust
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100