brasa-template-writer

To migrate legacy brasa YAML templates, the Skill analyzes old reader.function and handler-based fields, applies transformation rules, and aligns the output with the official pipeline schema for production-ready data pipelines.

A brasa YAML template defines data pipelines for ETL processing. You need to create one when configuring new data sources or modernizing legacy ETL configurations to ensure frontmatter requirements like name and description are met.

Converting old brasa ETL configurations requires identifying reader.function and handler-based fields in legacy templates, then applying migration rules and pipeline writer blocks to transform them into the modern pipeline-based format.

Yes, when creating a new brasa YAML template, you can include optional component directories such as scripts, references, and assets to support your data pipeline configuration and ensure production-ready outputs.

Yes, the brasa template migration process features mode detection that automatically identifies whether to write a new template from scratch or migrate an existing legacy template based on the presence of reader.function and handler fields.

Migration limitations include dependency on the official pipeline schema structure; templates lacking required frontmatter fields like name and description will fail alignment, and unsupported legacy reader formats may need manual transformation before applying pipeline writer blocks.