opendevstack / opendevstack/ods-core
When some ODS service is not available in a Box, the solution should not always be restart the whole ODS infrastructure.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 53
- Forks
- 34
- Avg merge
- 3h 26m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when I have to restart the whole ODS infrastructure just because a service is down.
Describe the solution you'd like
An script checking if all services are up and restarting only the ones it finds down.
Describe alternatives you've considered
N/A
Additional context
If you are running e2e tests, you waste a lot of time for each service it finds down.
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 locating the existing ODS infrastructure and service-management scripts for a Box, then identify how service availability and restarts are currently handled. Done means a script detects unavailable services and restarts only those services, without restarting the whole infrastructure; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100