Optional SIGTERM at Job Failure
Open
question
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
I would like to THANK YOU for this brilliant piece of software!
I have a use case in which `supercronic` acts as the entry-point of a container. That leads to the necessity to restart the container if the job that is run by `supercronic` fails.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name any files, tests, or entry points. Clarify when supercronic should send SIGTERM after a job failure, how this should be configured, and what the expected container behavior and tests should demonstrate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100