Convert YML to TSV

Why Convert YML to TSV?

Converting YML files to TSV format transforms hierarchical DevOps configuration data into flat tabular structures that can be directly imported into spreadsheets, databases, and data analysis tools. YML is the standard extension for Docker Compose files, CI/CD pipelines, and Ansible playbooks, but when you need to analyze, filter, or aggregate that configuration data in Excel or a database, TSV provides the ideal intermediate format.

This conversion is particularly valuable for infrastructure teams that need to audit configurations across multiple services. For example, converting a docker-compose.yml into TSV lets you import service definitions into a spreadsheet where you can sort by image name, filter by port mapping, or create pivot tables summarizing resource allocations. Similarly, converting Ansible inventory YML files to TSV enables bulk analysis of host configurations.

Our converter intelligently flattens YML hierarchies into tabular rows: each key-value pair becomes a row with columns for the key path, value, and parent context. Nested mappings are represented using dot-notation paths (e.g., services.web.image), and sequences are expanded into individual rows. This approach preserves the full data context while making it accessible in a two-dimensional tabular format.

TSV is preferred over CSV for this conversion because tab characters almost never appear in YML configuration values, eliminating the need for quoting and escaping that CSV requires. The result is a cleaner, more predictable output that imports flawlessly into any spreadsheet or database system.

Key Benefits of Converting YML to TSV:

• Spreadsheet Import: Directly open in Excel, Google Sheets, or LibreOffice Calc with automatic column detection
• Database Loading: Use MySQL LOAD DATA, PostgreSQL COPY, or SQLite .import to bulk-load configuration data
• Data Analysis: Analyze configurations with pandas, R, or other statistical tools
• Configuration Auditing: Sort, filter, and pivot configuration values across multiple services
• No Quoting Issues: TSV avoids the CSV quoting/escaping complexity since tabs rarely appear in config values
• Bulk Comparison: Compare configurations side-by-side in spreadsheet format
• Report Generation: Create summary reports from configuration data using spreadsheet formulas

Practical Examples

Example 1: Docker Compose Service

Input YML file (docker-compose.yml):

version: "3.8"
services:
  web:
    image: nginx:latest
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./html:/usr/share/nginx/html
    restart: always

Output TSV file:

Key	Value	Path	Type
version	3.8	root	scalar
image	nginx:latest	services.web	scalar
ports[0]	80:80	services.web	sequence
ports[1]	443:443	services.web	sequence
volumes[0]	./html:/usr/share/nginx/html	services.web	sequence
restart	always	services.web	scalar

Example 2: CI/CD Pipeline Configuration

Input YML file (.gitlab-ci.yml):

stages:
  - build
  - test
  - deploy

build_job:
  stage: build
  script:
    - npm install
    - npm run build
  artifacts:
    paths:
      - dist/

Output TSV file:

Key	Value	Path	Type
stages[0]	build	root	sequence
stages[1]	test	root	sequence
stages[2]	deploy	root	sequence
stage	build	build_job	scalar
script[0]	npm install	build_job	sequence
script[1]	npm run build	build_job	sequence
paths[0]	dist/	build_job.artifacts	sequence

Example 3: Ansible Inventory

Input YML file (inventory.yml):

all:
  hosts:
    web1:
      ansible_host: 192.168.1.10
      ansible_user: deploy
    web2:
      ansible_host: 192.168.1.11
      ansible_user: deploy
    db1:
      ansible_host: 192.168.1.20
      ansible_user: admin

Output TSV file:

Key	Value	Path	Type
ansible_host	192.168.1.10	all.hosts.web1	scalar
ansible_user	deploy	all.hosts.web1	scalar
ansible_host	192.168.1.11	all.hosts.web2	scalar
ansible_user	deploy	all.hosts.web2	scalar
ansible_host	192.168.1.20	all.hosts.db1	scalar
ansible_user	admin	all.hosts.db1	scalar

Frequently Asked Questions (FAQ)

Q: What is YML format?

A: YML is the short file extension for YAML (YAML Ain't Markup Language), a human-readable data serialization standard following the YAML 1.2 specification. It is the dominant extension for Docker Compose files (docker-compose.yml), CI/CD configurations (.travis.yml, .gitlab-ci.yml), Rails configuration (database.yml), Ansible playbooks, and Helm charts. YML uses indentation-based structure with key-value pairs, sequences, and nested mappings.

Q: What is TSV format?

A: TSV (Tab-Separated Values) is a plain text tabular data format where columns are separated by tab characters and rows are separated by newlines. Registered with IANA as text/tab-separated-values, TSV is widely used in bioinformatics, database operations, and data analysis. Unlike CSV, TSV avoids quoting ambiguity because tab characters rarely appear within data fields, making it a cleaner and more predictable format for data exchange.

Q: How is hierarchical YML data flattened into TSV rows?

A: The converter flattens nested YML structures using dot-notation paths. For example, a value at services.web.image in YML becomes a row with the key "image", value "nginx:latest", and path "services.web". Sequences are expanded into individual rows with array index notation (e.g., ports[0], ports[1]). This preserves the full context of each value while fitting it into a two-dimensional table.

Q: Can I import the TSV output directly into Excel or Google Sheets?

A: Yes. TSV files are natively supported by Microsoft Excel, Google Sheets, and LibreOffice Calc. Simply open the .tsv file and the columns will be automatically detected using tab delimiters. No import wizard or delimiter configuration is needed in most cases.

Q: Why use TSV instead of CSV for YML conversion?

A: TSV is preferred for YML conversion because YML configuration values frequently contain commas (e.g., port mappings "80:80", environment lists) which would require quoting and escaping in CSV format. Tab characters almost never appear in configuration values, so TSV produces cleaner output without quoting complications.

Q: What happens to YAML anchors and aliases in the YML file?

A: YAML anchors (&) and aliases (*) are fully resolved during parsing. The TSV output contains the expanded values, so inherited configurations (like database.yml using &default and *default) will show all values explicitly in the tabular output.

Q: Are YML comments preserved in the TSV output?

A: YML comments (lines starting with #) are preserved as separate rows in the TSV output with a "comment" type marker. This ensures important documentation within your configuration files is not lost during the conversion to tabular format.

Q: What happens if my YML file has syntax errors?

A: If the YML file contains syntax errors such as incorrect indentation or invalid characters, the converter will treat the content as plain text and output each line as a single-column TSV row. You will still receive a valid TSV file, though the structured column mapping will not be applied.

Q: Is there a file size limit?

A: Our converter handles YML files of any reasonable size. Complex configurations with deeply nested structures, multiple services, and extensive key-value mappings are fully supported and produce well-organized TSV output suitable for spreadsheet and database import.