What YAML is
YAML uses indentation instead of brackets. It is a superset of JSON, supports comments, and is meant to be edited by hand.
Kubernetes manifests, CI pipelines, Ansible playbooks and most modern config files.
What Firebase is
JSON shaped for a Realtime Database import: an object keyed by record id rather than an array.
Firebase projects.
What changes when you convert YAML to Firebase
A YAML list of maps reads as rows and columns directly. Anchors and aliases are resolved before the table is built, so a repeated block arrives expanded rather than as a reference.
Keys come from the first column. Firebase does not store arrays natively, so a keyed object is the correct shape for an import.
What carries over from YAML to Firebase
One property of the YAML has no home in Firebase, and it is worth knowing which before you convert.
An empty cell and a missing one are the same thing in Firebase, so a null and an empty string in the YAML both come out blank and can no longer be told apart.
Both formats record types, so numbers, booleans and nulls survive as themselves rather than as text.
The identifier 007 comes out of the Firebase as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.
The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a Firebase file goes wrong.
The quotes around Jonah "Jo" Pryce are escaped with a backslash in the Firebase.