dbt-meshify split creates a funk-ily formatted dbt_project.yml file

[graciegoheen]

Describe the bug

This is nit-picky, but have gotten feedback that it's important to prevent as many manual "fixes" as possible.

When I run the dbt-meshify split command and a new subproject is generated, the dbt_project.yml file that is creates has a weird format. It would be nice if we used the same dbt_project.yml format you get when you run a dbt init to create a new project.

Steps to reproduce

• run dbt-meshify split command

Expected results

• a dbt_project.yml file is created with the typical dbt yml format (same as when you run dbt-init)

Actual results

• a dbt_project.yml file is created with an odd format

Screenshots and log output

System information

Which database are you using dbt with?

• postgres
• redshift
• bigquery
• snowflake
• other (specify: ____________)

The output of dbt debug:

<output goes here>

The output of dbt --version:

<output goes here>

Additional context

Are you interested in contributing the fix?

[graciegoheen]

Another thing I found odd here, was that only the folders that we're copying over are create.

In my case, there was no empty folder for tests, seeds, macros, etc. that I'd expect when running a dbt init.

[graciegoheen]

I'd also potentially expect for my .gitignore file to be copied over and an empty / template README to be created

[dave-connors-3]

oh yeah it's funky as hell 😄 I don't know how much leeway the yml library we're using is going to give us to format the project yml the way we're used to seeing. Very open to suggestions

I'm going to split your folder and other project files suggestion into a separate issue!

[graciegoheen]

Is there any reason to not just do a dbt init in the new project before pulling stuff over? Is that a better place to start from for a new project? Or is empty easier?

[graciegoheen]

Elize also requested copying over the sqlfluff config file

[nicholasyager]

Completed in #206