Challenge · beginner · 20 min · Free account
The config that lies
Halvard's receiver has three places a timeout can come from and they disagree. Work out which value actually runs, why the one in the repo is not it, and put the right value in the layer that wins.
Brief
- Customer
- Halvard Freight (synthetic customer; every file and log on this box is made up for the exercise)
- Situation
- The receiver's billing call is timing out at 5 seconds and creating retries, although
config.yamlin the repo says 30. A colleague changed the file yesterday and restarted the service; nothing changed. The service reads a config file, an environment file loaded by systemd, and accepts a command-line flag, and the README explains which wins. - Your role
- You are the FDE on the Halvard engagement. You may read everything, edit any config layer, and run the receiver's config resolver. The console binds the resolved value to the live receiver.
- Goal
- Name the value the receiver actually runs with and the layer it came from, set the right value in the layer that wins, and show the resolver and the live service agreeing.
Objectives
- 1.Name the timeout the receiver actually runs with (you commit to an answer)
- 2.Name the layer that supplied it (you commit to an answer)
- 3.Remove the stale override so the documented value runs, and keep the token
- 4.Show the resolver reporting 30 from config.yaml
Mission workspace
This mission opens with a free account. The brief above is the whole problem; the box, the hints and the debrief are behind sign-in.
a free account unlocks the core curriculum tier · no card