ironcore-dev / ironcore-dev/boot-operator

Use a mock registry server in test suite

Open
#189 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/metal-automation
Dominant language
Go
Stars
6
Forks
9
Avg merge
19h 5m
Merged PRs (30d)
10

Description

What would you like to be added:

We are currently relying on a real OS image from ghcr.io to be pulled as part of the test suite. This creates an unnecessary external dependancy which might create frictions in test stability in the future.

Why is this needed:

In order to use a real image, we should rather start a localhost registry provider a dummy OCI manifest which can be fetched from the operator to extract the neccessary layers for the IPXEBootConfig and HTTPBootConfig.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the test suite that pulls the OS image from ghcr.io and the code extracting layers for IPXEBootConfig and HTTPBootConfig. Add a localhost registry serving a dummy OCI manifest, then verify the tests no longer depend on ghcr.io and still extract the required layers successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.