Add support for transient timers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 338
- PR merge metrics
- No merged PRs in 30d
Description
systemd-run supports creating units that run on a schedule instead of immediately.
This is implemented by creating a timer unit alongside the service that executes the command.
While creating persistent timers and services is certainly an option, they create manual cleanup overhead.
It would be very useful to support such a feature in go-systemd, similar to systemd-run's --timer-property= option.
Similarly, systemd-run also supports creating transient socket and path units that launch the command service when triggered. These would also be useful.
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
The issue names no repository files or tests. Start by comparing systemd-run's --timer-property= behavior with the existing go-systemd APIs; done means go-systemd can create transient timer, socket, and path units that trigger a command service without persistent-unit cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100