Skip to main content

No + prefix on resource paths

Fusion-only flag

This behavior change flag is specific to Fusion and has no equivalent in dbt Core.

require_resource_names_without_plus_prefixFusion
Introduced2.0.0-preview.208
Matured (default → true)—
Removed—

The require_resource_names_without_plus_prefix flag is set to false by default.

In dbt_project.yml, the + prefix marks a config, while a key without the prefix is treated as part of a resource path (a folder or file name). dbt historically accepted resource paths that start with + (for example, a folder named +my_folder under models) even though the + prefix is meant for configs only. This is accidental behavior that produces misleading error messages when a config is missing its + prefix, because dbt can't reliably tell whether a +-prefixed key is a folder name or a mistyped config.

When the require_resource_names_without_plus_prefix flag is set to false, dbt raises a warning for each resource path that starts with +:


[warning] [InvalidConfig (dbt1005)]: Resource path `snapshot_contract.+path_1` in dbt_project.yml starts with `+`. This will be deprecated in future versions of dbt.

When the flag is set to true, dbt treats a +-prefixed key as an unrecognized config key and raises an error instead:


[error] [SerializationError (dbt1013)]: Invalid model definition `snapshot_contract.+path_1`: Unrecognized key `snapshot_contract.+path_1`. Custom keys must go under `+meta`.

To resolve the warning or error, remove the + prefix from any folder or file name in dbt_project.yml. For custom keys, nest them under +meta.

For example, name the resource path so it doesn't start with +:

dbt_project.yml

models:
  my_project:
    my_folder:        # resource path — no + prefix
      +enabled: true  # config — keep the + prefix

Was this page helpful?

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

0