spinframework / spinframework/spin-operator
Support for Non-HTTP Triggers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
One thing that would be incredibly value in a kubernetes deployment is the ability to use alternative triggers - this is currently blocked on https://github.com/deislabs/containerd-wasm-shims/issues/193 - but we should run through a hypothetical example to understand if we're over-optimizing our api surface towards http.
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 blocked containerd-wasm-shims issue 193 and the hypothetical Kubernetes deployment scenario described here. Determine whether supporting non-HTTP triggers would require expanding Spin Operator’s API surface, and document a concrete example if the approach is viable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, wasm
- Domain
- backend-api-design, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100