Close Menu
    DevStackTipsDevStackTips
    • Home
    • News & Updates
      1. Tech & Work
      2. View All

      From Data To Decisions: UX Strategies For Real-Time Dashboards

      September 13, 2025

      Honeycomb launches AI observability suite for developers

      September 13, 2025

      Low-Code vs No-Code Platforms for Node.js: What CTOs Must Know Before Investing

      September 12, 2025

      ServiceNow unveils Zurich AI platform

      September 12, 2025

      Building personal apps with open source and AI

      September 12, 2025

      What Can We Actually Do With corner-shape?

      September 12, 2025

      Craft, Clarity, and Care: The Story and Work of Mengchu Yao

      September 12, 2025

      Distribution Release: Q4OS 6.1

      September 12, 2025
    • Development
      1. Algorithms & Data Structures
      2. Artificial Intelligence
      3. Back-End Development
      4. Databases
      5. Front-End Development
      6. Libraries & Frameworks
      7. Machine Learning
      8. Security
      9. Software Engineering
      10. Tools & IDEs
      11. Web Design
      12. Web Development
      13. Web Security
      14. Programming Languages
        • PHP
        • JavaScript
      Featured

      Optimizely Mission Control – Part III

      September 14, 2025
      Recent

      Optimizely Mission Control – Part III

      September 14, 2025

      Learning from PHP Log to File Example

      September 13, 2025

      Online EMI Calculator using PHP – Calculate Loan EMI, Interest, and Amortization Schedule

      September 13, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      sudo vs sudo-rs: What You Need to Know About the Rust Takeover of Classic Sudo Command

      September 14, 2025
      Recent

      sudo vs sudo-rs: What You Need to Know About the Rust Takeover of Classic Sudo Command

      September 14, 2025

      Dmitry — The Deep Magic

      September 13, 2025

      Right way to record and share our Terminal sessions

      September 13, 2025
    • Learning Resources
      • Books
      • Cheatsheets
      • Tutorials & Guides
    Home»Development»YAML files in DBT

    YAML files in DBT

    June 12, 2025

    To make streamline project development and maintenance, in any programming language, we need the support of metadata, configuration, and documentation. Project configurations can be done using configuration files. Configuration files are easy to use and make it user friendly to interact with developer. One such type of configuration files used in DBT are the YAML files.
    In this blog, will go through the required YAML files in DBT.
    Let’s understand first what YAML is and DBT

    DBT (Data Build Tool) :
    Data transformation is the important process in modern analytics. DBT is a system to transform, clean and aggregate data within data warehouse. The power of DBT lies in its utilization of YAML files for both configuration and transformation.
    Note:
    Please go through link for DBT(DBT)
    What is YAML file:
    YAML acronym as “Yet Another Markup Language.” It is easy to read and understand. YAML is superset of JSON.
    Common use of YAML file:
    – Configuration Management:
    Use to define configuration like roles, environment.
    – CI/CD Pipeline:
    CI/CD tools depend on YAML file to describe their pipeline.
    – Data Serialization:
    YAML can manage complex data types such as linked list, arrays, etc.
    – API:
    YAML can be use in defining API contracts and specification.

    Sample Example of YAML file:
    Pictureyaml
    YAML files are the core of defining configuration and transformation in DBT. YAML files have “.yml” extension.

    The most important YAML file is
    profiles.yml:
    This file needs to be locally. It contains sensitive that can be used to connect with target data warehouse.
    Purpose:
    It consists of main configuration details to which connect with data warehouse(Snowflake, Postgres, etc.)
    profile configuration looks like as :
    Picturedbtdemo
    Note:
    We should not share profiles.yml file with anyone because it consists of target data warehouse information. This file will be used in DBT core and not  in DBT cloud.
    YAML file classification according to DBT component:
    Let us go through different components of DBT with corresponding YAML files:

    1.dbt_project.yml:
    This is the most important configuration file in DBT. This file tells DBT what configuration
    need to use for projects. By default, dbt_project.yml is the current directory structure

    For Example:

    name: string
    
    config-version: 2
    version: version
    
    profile: profilename
    
    model-paths: [directorypath]
    seed-paths: [directorypath]
    test-paths: [directorypath]
    analysis-paths: [directorypath]
    macro-paths: [directorypath]
    snapshot-paths: [directorypath]
    docs-paths: [directorypath]
    asset-paths: [directorypath]
    
    packages-install-path: directorypath
    
    clean targets: [directorypath]
    
    query-comment: string
    
    require-dbt-version: version-range | [version-range]
    
    flags:
      <global-configs>
    
    dbt-cloud:
      project-id: project_id # Required
      defer-env-id: environment # Optional
    
    exposures:
      +enabled: true | false.
    
    quoting:
      database: true | false
      schema: true | false
      identifier: true | false
    
    metrics:
      <metric-configs>
    
    models:
      <model-configs>
    
    seeds:
      <seed-configs>
    
    semantic-models:
      <semantic-model-configs>
    
    saved-queries:
      <saved-queries-configs>
    
    snapshots:
      <snapshot-configs>
    
    sources:
      <source-configs>
      
    tests:
      <test-configs>
    
    vars:
      <variables>
    
    on-run-start: sql-statement | [sql-statement]
    on-run-end: sql-statement | [sql-statement]
    
    dispatch:
      - macro_namespace: packagename
        search_order: [packagename]
    
    restrict-access: true | false
    

     

    Model:
    Models use SQL language that defines how your data is transformed .In a model, configuration file, you define the source and the target tables and their transformations. It is under the model directory of DBT project, and we can give name as per our convenience.
    Below is the example:
    Picturemodel   This is the YAML file in model. Given name as “schema.yml”
    Purpose of model YML file:
    It configures the model level metadata such as tags, materialization, name, column which use for transforming the data
    It looks like as below:

    version: 2
    
    models:
      - name: my_first_dbt_model
        description: "A starter dbt model"
        columns:
          - name: id
            description: "The primary key for this table"
            data_tests:
              - unique
              - not_null
    
      - name: my_second_dbt_model
        description: "A starter dbt model"
        columns:
          - name: id
            description: "The primary key for this table"
            data_tests:
              - unique
              - not_null
    
    
    

    2.Seed:
    Seeds used to load CSV files into data model. This is useful for staging before applying any
    transformation.
    Below is the example:
    Pictureseeds

    Purpose of Seeds YAML file:
    To define the path of CSV file under seed directory and which column needs to transform in CSV file and load into the data warehouse tables.

    Configuration file looks like as below:

    version: 2
    seeds:
      - name: <name>
        description: Raw data from a source
        database: <database name>
        schema: <database schema>
        materialized: table
        sql: |-
          SELECT
            id,
            name
          FROM <source_table>
    
    

    Testing:
    Testing is a key step in any project. Similarly, DBT create test folder to test unique constraints, not null values.

    Create dbtTest.yml file under test folder of DBT project

    And it looks like as below:

    Picturetest
    Purpose of test YML file as:
    It helps to check data integrity quality and separates from the business logic
    It looks like as below:

    columns:
      - name: order_id
        tests:
          - not_null
          - unique
    
    

    As we go through different YAML files in DBT and purpose for the same.

    Conclusion:
    dbt and its YAML files provide human readable way to manage data transformation. With dbt, we can easily create, transform, and test the data models and make valuable tools for data professionals. With both DBT and YAML, it empowers you to work more efficiently as data analyst. Data engineers or business analysts

    Thanks for reading.

     

     

     

    Source: Read More 

    Facebook Twitter Reddit Email Copy Link
    Previous ArticleWhy AI-Led Experiences Are the Future — And How Sitecore Stream Delivers Them
    Next Article Developing a Serverless Blogging Platform with AWS Lambda and Python

    Related Posts

    Repurposing Protein Folding Models for Generation with Latent Diffusion
    Artificial Intelligence

    Repurposing Protein Folding Models for Generation with Latent Diffusion

    September 14, 2025
    Artificial Intelligence

    Scaling Up Reinforcement Learning for Traffic Smoothing: A 100-AV Highway Deployment

    September 14, 2025
    Leave A Reply Cancel Reply

    For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

    Continue Reading

    CVE-2025-42963 – SAP NetWeaver Application Server for Java Java Object Deserialization Remote Code Execution Vulnerability

    Common Vulnerabilities and Exposures (CVEs)

    Mirai Botnets Exploit Flaw in Wazuh Security Platform

    Security

    Rebranded VS Code extension Eyecons – an icon theme, where icon colors are adapted to the colors theme

    Development

    Advanced Application Architecture through Laravel’s Service Container Management

    Development

    Highlights

    CVE-2024-30152 – HCL SX Cryptographic Weakness

    April 25, 2025

    CVE ID : CVE-2024-30152

    Published : April 25, 2025, 6:15 p.m. | 46 minutes ago

    Description : HCL SX v21 is affected by usage of a weak cryptographic algorithm. An attacker could exploit this weakness to gain access to sensitive information, modify data, or other impacts.

    Severity: 6.5 | MEDIUM

    Visit the link for more details, such as CVSS details, affected products, timeline, and more…

    CVE-2025-23104 – Samsung Mobile Processor Exynos Use-After-Free Privilege Escalation Vulnerability

    June 2, 2025

    NetScaler deelt Indicators of Compromise (IoCs) CVE-2025-5777

    July 17, 2025

    CVE-2025-3628 – Moodle Anonymous Assignment De-Anonymization Vulnerability

    April 25, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.