Icinga / Icinga/icinga-testing
Evaluate Testcontainers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 2
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 11
Description
I recently stumbled upon a project called Testcontainers that looks an awful lot like what I've built in this repository:
I haven't looked into this in any detail, but it looks promising at first glance. Using the Docker Go package as a client library didn't really spark joy and there happened a lot of changes to that package (remember Moby?), which this project hasn't caught up to (it uses a quite old version of that package). Maybe Testcontainers might be a way forward here, using an external library for the annoying parts and keeping the Icinga-specific bootstrapping parts and convenience helpers in this repo.
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 linked testcontainers-go project and the repository's current use of the Docker Go package. Compare whether Testcontainers can replace the existing client while preserving the Icinga-specific bootstrapping and convenience helpers mentioned in the issue. Done means documenting an informed evaluation and a clear direction for the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- testing-qa, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100