opensafely-core / opensafely-core/sysadmin
move otel-collector to its own repo
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
- this has grown a bit & it may now be more convenient to manage in its own repo
- we recently had an issue where broken tests in an unrelated CI test in the sysadmin repo blocked us from merging an urgent update to otel-collector
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 the otel-collector components and CI tests in the sysadmin repository, then examine how they are currently managed and deployed. The issue is complete only when the repository move, ownership, and CI boundaries are defined and the collector no longer depends on unrelated sysadmin checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100