YAML ↔ JSON Converter

Most infrastructure tooling speaks YAML — Kubernetes, Docker Compose, GitHub Actions, Ansible — while most APIs speak JSON. Sooner or later you need to move a snippet between the two, and this does that conversion with live syntax checking so you catch a malformed block before it goes anywhere near a cluster.

Why the split exists

• YAML — supports comments, uses indentation instead of braces, and generally reads more like configuration a human is meant to maintain by hand. That's exactly why config-heavy tools (Kubernetes manifests, CI pipelines, Ansible playbooks) default to it.
• JSON — stricter syntax, no comments, but universally supported and easy to generate and parse programmatically — which is exactly what you want for a payload passed between two programs rather than edited by a person.

The mistakes that actually cost you time

• Tabs — YAML requires spaces for indentation. A stray tab, often invisible in an editor, produces a parse error that can take longer to spot than it should.
• The boolean gotcha — under YAML 1.1, bare yes, no, on and off parse as booleans, not strings. A hostname literally called no, or a country code that happens to be NO, will silently become false unless you quote it.
• Unquoted colons and hashes — a value containing a colon or a hash symbol needs quoting, or the parser will read part of it as new structure or a comment.
• Multiline strings — | keeps newlines intact, > folds them into spaces. Using the wrong one is a common source of a script that "looks right" in the YAML file but runs differently than expected.

None of these are exotic edge cases — they're the actual reasons a Kubernetes manifest that "looked fine" fails to apply, or an Ansible variable evaluates to the wrong thing. Running it through a strict parser before it goes anywhere near production catches all of them up front.