Clarify that meta is no longer "always" available as a top-level key

dbt-labs · Oct 7, 2023 · bee4a9b · bee4a9b
1 parent abfd0b2
commit bee4a9b
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/website/docs/reference/resource-configs/meta.md b/website/docs/reference/resource-configs/meta.md
@@ -207,7 +207,7 @@ semantic_models:
 ## Definition
 The `meta` field can be used to set metadata for a resource. This metadata is compiled into the `manifest.json` file generated by dbt, and is viewable in the auto-generated documentation.
 
-Depending on the resource you're configuring, `meta` may be available within the `config` property, or as a top-level key. (For backwards compatibility, `meta` is always supported as a top-level key, though without the capabilities of config inheritance.)
+Depending on the resource you're configuring, `meta` may be available within the config property, and/or as a top-level key. (For backwards compatibility, `meta` is often (but not always) supported as a top-level key, though without the capabilities of `config` inheritance.)
 
 
 ## Examples