spinframework / spinframework/spin
Add `spin up --trigger-type` flag
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
spin up can run multiple trigger executors for an app. It would be useful in some scenarios to run only certain trigger type(s), e.g. I want to test http triggers but I don't have a redis host to serve redis triggers, or I want to run http triggers on one host and redis triggers on a different one.
A new --trigger-type flag could serve this purpose:
# Run only 'http' triggers
$ spin up --trigger-type http
As an added bonus, this would give a mechanism to run "manifest-less" components (ref #2479) with non-'http' triggers.
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 reading the spin up command implementation and the code that selects trigger executors. Trace how multiple trigger types are started, then define completion as spin up --trigger-type http running only HTTP triggers while preserving the existing behavior when the flag is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100