[Discussion] Do we want to support systems without the Connectivity Service?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 5
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 10
Description
The listrev Single-App integration test case did not use the Connectivity Service because the whole system was contained in a single app, and no network connections were needed. drunc, however, has grown a dependency on the CS for its own control channels.
Two items:
- Should
druncsupport systems that do not use the Connectivity Service? What functionality do these systems implement that make running a CS (even if only fordruncprocesses) problematic? - In the case that a Connectivity Service server is not found, we may want to improve the log messages (error boxes) printed by
drunc, to make it more clear that this is what is happening.
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 reviewing drunc's dependency on the Connectivity Service for control channels and compare it with the listrev Single-App integration test, which runs without that service. Determine which no-CS systems need support and what clearer error boxes should communicate when a server is unavailable. Done requires an agreed scope and corresponding validation approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100