oasisprotocol / oasisprotocol/oasis-core
Support reloading bundles without restarting `oasis-node`
Open
Nobody has claimed this yet.
c:cli
c:runtime
c:runtime/scheduler
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
SUMMARY
Currently, there is no way to manually reload the bundle (e.g ROFL .orc) without restarting the whole oasis-node service. This is useful:
- when you're bugfixing your ROFL and don't want to make a new release+deployment each time
- when you're bugfixing your ROFL and don't use the new scheduler at all
- in the Localnet in "watch" mode, where your rofl folder is bind-mounted and a script would monitor any .orc updates to reload it automatically
I suggest sth like oasis-node control reload-bundle <path>
ISSUE TYPE
- Feature Idea
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 at the oasis-node control command entry point and trace how bundles are loaded during service startup. Check how the proposed reload-bundle command could trigger the same behavior without restarting the service, then verify that a changed bundle can be reloaded and that the existing service remains running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100