YAML Path Finder
Lists every leaf path in a configuration with its type and value, so a single setting can be named exactly.
Loading the tool…
Processing happens locally in your browser.
What you paste or load is processed by this page and is not uploaded to a server. Nothing is stored unless you use a control that says it stores something, and you can clear anything this site has kept from the privacy page.
How to use this tool
- Paste the configuration you want to explore.
- Select List paths.
- Find the setting you care about and copy its full path — that is what to quote in a ticket, a runbook or a command-line override.
What yaml path finder does
Deeply nested configuration is hard to talk about. "The memory limit" is ambiguous when three containers each have one; spec.template.spec.containers[0].resources.limits.memory is not. This tool walks the document and lists every leaf with its full path, its type and its value.
The type column is the part that repays attention. It shows what YAML decided each unquoted value is, so a version that should be a string and is shown as a number, or a region code shown as a boolean, is visible immediately — and the fix is to quote it in the source.
Frequently asked questions
What YAML decided each unquoted value is. It is the fastest way to spot a value that should be a string and is being read as a number or a boolean, which is the cause of a surprising share of configuration bugs.
They are written the way most tools expect — dotted with bracketed indexes — so they usually paste straight into a --set flag or a lookup. Check the exact syntax your tool wants, because a few use slashes or a different index form.
Because a leaf is where a value lives, and that is what people are looking for. The intermediate keys are visible in every path that passes through them, so listing them separately would add rows without adding information.