Conversation
noahmoss
changed the title
noahmoss
force-pushed
the
nm/commence-restore-service
branch
from
September 28, 2026 21:03
f2b5d1a to
06a7e93
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Adds a
commence-restore.serviceservice file similar to the existingcommence-backup.service(with slight differences).First implementation step for RFC:
commence-restore.serviceWhat is the current behavior?
admin-mgr commence-restoreis invoked directly by admin-api and runs in the same cgroup.What is the new behavior?
Nothing new as a direct result of this PR, but puts the pieces into place for running
commence-restoreas a standalone service withType=notify