`dbt_project.yml` sets a custom schema about dbt_artifacts HOT 3 CLOSED

I also noticed it today. The custom schema we define in our dbt_project.yml as described in step 2 here gets overwritten by the one defined in https://github.com/tailsdotcom/dbt_artifacts/blob/main/dbt_project.yml#L8

Edit: I figured it out - I added the dbt_artifacts model one level too deep in my dbt_project.yml, moving it one level up actually solved the issue.

from dbt_artifacts.

I suspect the thinking was to have some default schema defined, rather than have the models appear in the projects default schema if not overridden. We override this in our project, so happy to take this default out if that is 'best practice'.

from dbt_artifacts.

I am not able to configure a custom schema.Can somebody please help with this?
I am getting still Public schema used when I run dbt run -m dbt_artifacts.
I have set dbt_artifacts schema name and materialization but still, i am getting models been built under Public Schema.
My Configuration below in dbt project (dbt_project.yml)
# DBT_ARTIFACTS ----------------------------------------
dbt_artifacts:
+schema: dbt_artifacts
+materialized: table
incremental:
+schema: dbt_artifacts
+materialized: incremental
staging:
+schema: dbt_artifacts
+materliazed: view

from dbt_artifacts.