# Wildcard in dbt\_project.yml

**URL:** <https://discourse.getdbt.com/t/wildcard-in-dbt-project-yml/6621>\
**Category:** Help\
**Tags:** dbt\_project-yml\
**Created:** [February 6, 2023, 8:31am UTC](https://discourse.getdbt.com/t/wildcard-in-dbt-project-yml/6621 "2023-02-06T08:31:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dariusz](https://avatars.discourse-cdn.com/v4/letter/d/7ea924/32.png) [@Dariusz](https://discourse.getdbt.com/u/Dariusz)\
**Post date:** [February 6, 2023, 8:31am UTC](https://discourse.getdbt.com/t/wildcard-in-dbt-project-yml/6621/1 "2023-02-06T08:31:08Z")

</div>

## The problem I’m having

We are having a lot of models, tests and macros. The default structure became hard to navigate, that’s why we would like to change the dbt\_project.yml definitions so we could keep the related models, tests, seeds and macros in same directory for example

```auto
root
-> a
--> model
---> a.sql
--> test
---> a_test.sql

```

That would be possible, if dbt\_project.yml accepted wildcards we could do sth like

```auto
models:["root/**/model"]
tests:["root/**/test"]

```

## What I’ve already tried

I have already tried \*, \*_, ._

Is there anyway we could generate the dbt\_project.yml before execution? I could write an appropriate script for that.