feat: SSH executor / yip on remote devices
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 34
- Avg merge
- 14h 10m
- Merged PRs (30d)
- 5
Description
As title states, curious on your thoughts (@mudler) and Kairos team on implementation of https://github.com/mudler/yip but with an added ability to spawn an executor on remote devices.
Technically, this would look like modifying the current executor interface and having a LocalExecutor and a RemoteExecutor with guard rails around what can / cant run on remote devices.
Some technical issues that this might introduce is building in diskfs/go-diskfs and possibly trying to gate some of this behavior on "remotes" as some plugins will not work cross platform (ARM -> AMD).
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 reading yip's current executor interface and the proposed LocalExecutor/RemoteExecutor split. Review how diskfs/go-diskfs and plugins behave across remote devices and ARM-to-AMD execution; the work is complete when the remote execution scope, guard rails, and cross-platform limitations are defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100