Based on the knowledge sources, the recommended way to disable the upload of the

dbt_columns

artifact in Elementary is to use the variable

disable_dbt_columns_autoupload: true

in your

dbt_project.yml

, not

columns_upload_strategy

. The

columns_upload_strategy

variable is mentioned in troubleshooting for newer versions (e.g., 0.17.0), but for version 0.16.1, the correct approach is to use the

disable_dbt_columns_autoupload

variable. Here's how you should configure it:

yaml vars:   disable_dbt_columns_autoupload: true

This should prevent the

dbt_columns

artifact from being collected and uploaded. If you use

columns_upload_strategy: none

in 0.16.1, it will not have any effect, as this variable was introduced in later versions. If you still see the artifact being uploaded after setting

disable_dbt_columns_autoupload: true

, ensure you are on the correct package revision and that there are no typos in your configuration. Some users have reported that excluding the model directly (e.g.,

--exclude dbt_columns

) is a reliable workaround if the variable does not work as expected in your environment [Disable dbt_columns](https://slack.com/archives/C02CTC89LAX/p1698762841397829). In summary: - For Elementary 0.16.1, use

disable_dbt_columns_autoupload: true

. -

columns_upload_strategy

is not supported in 0.16.1. - If the variable does not work, exclude the model as a workaround. Let me know if you need more details or run into further issues!