Convert YML to CSV

Why Convert YML to CSV?

Converting YML files to CSV is valuable when you need to analyze, audit, or compare configuration data in a tabular format. YML files from Docker Compose, Kubernetes, Ansible, and CI/CD pipelines contain key-value pairs and nested structures that, when flattened into CSV rows, become easy to filter, sort, and analyze in spreadsheet applications like Excel or Google Sheets.

The .yml extension is standard across DevOps tooling: Docker Compose uses docker-compose.yml, GitHub Actions uses .yml workflows, Ruby on Rails stores all configuration in .yml files, and Ansible uses .yml playbooks. Converting these to CSV enables operations teams to create configuration inventories, audit environment variables, compare settings across environments, and import config data into databases or business intelligence tools.

Key Benefits of Converting YML to CSV:

• Configuration Auditing: List all keys and values from docker-compose.yml in a sortable spreadsheet
• Environment Comparison: Export configs from multiple .yml files to compare in Excel
• Database Import: Load flattened YML configuration into SQL databases for querying
• Data Analysis: Use pandas or R to analyze patterns in Ansible inventory .yml files
• Compliance Reporting: Generate tabular reports from Kubernetes manifest configurations
• Team Review: Share config data with non-technical stakeholders via spreadsheets

Practical Examples

Example 1: Docker Compose to Spreadsheet

Input YML file (docker-compose.yml):

version: "3.8"
services:
  web:
    image: nginx:latest
    ports:
      - "80:80"
      - "443:443"
  redis:
    image: redis:alpine

Output CSV file (docker-compose.csv):

key,value,parent
version,3.8,
services.web.image,nginx:latest,services.web
services.web.ports[0],80:80,services.web.ports
services.web.ports[1],443:443,services.web.ports
services.redis.image,redis:alpine,services.redis

Example 2: Ansible Inventory to Database

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 CSV file (inventory.csv):

key,value,parent
all.hosts.web1.ansible_host,192.168.1.10,all.hosts.web1
all.hosts.web1.ansible_user,deploy,all.hosts.web1
all.hosts.web2.ansible_host,192.168.1.11,all.hosts.web2
all.hosts.web2.ansible_user,deploy,all.hosts.web2
all.hosts.db1.ansible_host,192.168.1.20,all.hosts.db1
all.hosts.db1.ansible_user,admin,all.hosts.db1

Example 3: Spring Boot Application Config

Input YML file (application.yml):

server:
  port: 8080
  servlet:
    context-path: /api
spring:
  datasource:
    url: jdbc:postgresql://localhost:5432/mydb
    username: appuser
    password: secret
    driver-class-name: org.postgresql.Driver
  jpa:
    hibernate:
      ddl-auto: update
    show-sql: false
logging:
  level:
    root: WARN
    com.myapp: DEBUG

Output CSV file (application.csv):

key,value,parent
server.port,8080,server
server.servlet.context-path,/api,server.servlet
spring.datasource.url,jdbc:postgresql://localhost:5432/mydb,spring.datasource
spring.datasource.username,appuser,spring.datasource
spring.datasource.password,secret,spring.datasource
spring.datasource.driver-class-name,org.postgresql.Driver,spring.datasource
spring.jpa.hibernate.ddl-auto,update,spring.jpa.hibernate
spring.jpa.show-sql,false,spring.jpa
logging.level.root,WARN,logging.level
logging.level.com.myapp,DEBUG,logging.level

Frequently Asked Questions (FAQ)

Q: How does nested YML data convert to flat CSV?

A: The converter flattens the YML hierarchy using dot notation for nested keys. For example, services.web.image represents the image key nested under web under services. Lists use bracket notation like ports[0]. This preserves the full path to each value.

Q: Can I open the CSV output in Excel?

A: Yes. CSV files open natively in Microsoft Excel, Google Sheets, LibreOffice Calc, Apple Numbers, and virtually every spreadsheet application. You can sort, filter, and search through your YML configuration data using standard spreadsheet features.

Q: What happens to YML lists and arrays in CSV?

A: YML sequences (lists) are converted to individual CSV rows with indexed keys. For example, a ports list with two items becomes ports[0] and ports[1] as separate rows, each containing one value.

Q: Is there a difference between .yml and .yaml for CSV conversion?

A: No. Both extensions contain the same YAML format data. Docker Compose, GitHub Actions, and Rails all use .yml files, and the CSV conversion process is identical regardless of whether the file uses .yml or .yaml extension.

Q: Can I convert the CSV back to YML?

A: If the CSV preserves the dot-notation key paths, it can be reconstructed into YML. However, some information like comments and formatting preferences will be lost. Use our CSV to YML converter for the reverse operation.

Q: How are multi-line YML values handled in CSV?

A: Multi-line strings in YML are enclosed in double quotes in the CSV output, following the RFC 4180 standard. Newlines within quoted values are preserved, ensuring the data remains intact when imported into spreadsheets.

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

A: If the YML file contains syntax errors, the converter treats it as plain text and wraps the content in a single CSV cell. You will still get a valid output file that can be opened in any spreadsheet application.