Skip to main content
A security fix to the dbt Core component expands the set of keys that you can’t override using the Profile configuration in profiles.yml property. If you supply one of these keys, Maia ignores it and uses the connection-managed value instead, because overriding these keys could redirect the live warehouse connection or expose credentials. This is a breaking change for any pipeline that relies on overriding one of the newly restricted keys.

​
What’s changing

Identity and credential keys, such as user and password, were already protected. The newly restricted keys are the keys that control the connection target, the transport, and the authentication method. Any restricted key you supply in Profile configuration in profiles.yml is now ignored. Maia uses the value managed by your connection instead.

​
Restricted keys by cloud data warehouse

​
What you need to do

If you want to change any of the restricted values, update the connection itself. Don’t try to override them using Profile configuration in profiles.yml. Pipelines that still supply a restricted key continue to run. The key is ignored, and the value from your connection is used instead. We recommend that you review the Profile configuration in profiles.yml property of each dbt Core component in your pipelines and remove any restricted keys, so that your configuration reflects the values that are actually used.