Merge pull request #449 from dbt-labs/repo-sync

REPO SYNC - Public to Private

website/blog/2024-01-15-dbt-server-deprecation-announcement.md

@@ -0,0 +1,27 @@
+---
+title: "Deprecation of dbt Server"
+description: "Announcing the deprecation of dbt Server and what you need to know"
+slug: deprecation-of-dbt-server
+
+authors: [roxi_dahlke]
+
+tags: [dbt Server]
+hide_table_of_contents: false
+
+date: 2024-01-15
+is_featured: false
+---
+
+## Summary
+
+We’re announcing that [dbt Server](https://github.com/dbt-labs/dbt-server) is officially deprecated and will no longer be maintained by dbt Labs going forward. You can continue to use the repository and fork it for your needs. We’re also looking for a maintainer of the repository from our community! If you’re interested, please reach out by opening an issue in the [repository](https://github.com/dbt-labs/dbt-server/issues).
+
+## Why are we deprecating dbt Server?
+
+At dbt Labs, we are continually working to build rich experiences that help our users scale collaboration around data. To achieve this vision, we need to take moments to think about which products are contributing to this goal, and sometimes make hard decisions about the ones that are not, so that we can focus on enhancing the most impactful ones. 
+
+dbt Server previously supported our legacy Semantic Layer, which was [fully deprecated in December 2023](https://docs.getdbt.com/docs/dbt-versions/release-notes/Dec-2023/legacy-sl). In October 2023, we introduced the GA of the revamped dbt Semantic Layer with [significant improvements](https://www.getdbt.com/blog/build-centralize-and-deliver-consistent-metrics-with-the-dbt-semantic-layer), made possible by the [acquisition of Transform](https://www.getdbt.com/blog/dbt-acquisition-transform) and the integration of [MetricFlow](https://docs.getdbt.com/docs/build/about-metricflow) into dbt. 
+
+The dbt Semantic Layer is now fully independent of dbt Server and operates on MetricFlow Server, a powerful new proprietary technology designed for enhanced scalability. We’re incredibly excited about the new updates and encourage you to check out our [documentation](https://docs.getdbt.com/docs/use-dbt-semantic-layer/dbt-sl), as well as [this blog](https://www.getdbt.com/blog/how-the-dbt-semantic-layer-works) on how the product works.
+
+The deprecation of dbt Server and updates to the Semantic Layer signify the evolution of the dbt ecosystem towards more focus on in product and out-of-the-box experiences around connectivity, scale, and flexibility. We are excited that you are along with us on this journey. 

website/blog/authors.yml

@@ -430,6 +430,15 @@ ross_turk:
   name: Ross Turk
   organization: Datakin
 
+roxi_dahlke:
+  image_url: /img/blog/authors/roxi-dahlke.png
+  job_title: Product Manager
+  links:
+    - icon: fa-linkedin
+      url: https://www.linkedin.com/in/roxanna-dahlke-pourzand-445a3035
+  name: Roxi Dahlke 
+  organization: dbt Labs  
+
 sam_harting:
   description: Sam is a graduate of the inaugural Foundry Program. When Sam isn't helping clients build out their project, he is usually playing video games or making bad jokes to his friends, family, and coworkers.
   image_url: /img/blog/authors/sam-harting.png

website/docs/docs/collaborate/explore-projects.md

@@ -75,22 +75,16 @@ To interact with the full lineage graph, you can:
 
 
 ## Search for resources {#search-resources}
-With the search bar (on the upper left corner of the page or in a lineage graph), you can search with keywords or by using [node selection syntax](/reference/node-selection/syntax). The resources that match your search criteria will display as a lineage graph and a table in the main section of the page. 
-
-Select a node (single-click) in the lineage graph to highlight its relationship with your other search results and to display which project contains the resource's definition. When you choose a node (double-click) in the lineage graph or when you select a resource in the table, dbt Explorer displays the [resource's details page](#view-resource-details).
+With the search bar (on the upper left corner of the page or in a lineage graph), you can search with keywords or selectors. The resources that match your search criteria will display in a list (keyword search) or the lineage graph (selector search). 
 
 ### Search with keywords
-When searching with keywords, dbt Explorer searches through your resource metadata (such as resource type, resource name, column name, source name, tags, schema, database, version, alias/identifier, and package name) and returns any matches.
-
-- Keyword search features a side panel (to the right of the main section) to filter search results by resource type. 
-- Use this panel to select specific resource tags or model access levels under the **Models** option. 
-  - For example, a search for "sale" returns results that include all resources with the keyword "sale" in their metadata. Filtering by **Models** and **Sources** refines these results to only include models or sources.
+When searching with keywords, dbt Explorer searches through your resource metadata, such as resource name, and returns any matches. When searching for an exact column name, the results show all relational nodes containing that column in their schemas. If there's a match, a notice in the search result indicates the resource contains the specified column.
 
-- When searching for an exact column name, the results show all relational nodes containing that column in their schemas. If there's a match, a notice in the search result indicates the resource contains the specified column.
+You can then refine the search results using the filters in the panel on the right-hand side of the page. Use this panel to select specific resource types or tags to apply. You can filter on model properties (access or materialization type) under the **Models** option. 
 
 ### Search with selectors 
 
-You can search with [selectors](/reference/node-selection/methods). Below are the selectors currently available in dbt Explorer:   
+You can search with [selectors](/reference/node-selection/methods) within the full lineage graph using the search bar. Below are the selectors currently available in dbt Explorer:   
 
 - `fqn:` — Find resources by [file or fully qualified name](/reference/node-selection/methods#the-fqn-method). This selector is the search bar's default. If you want to use the default, it's unnecessary to add `fqn:` before the search term.
 - `source:` — Find resources by a specified [source](/reference/node-selection/methods#the-source-method).
@@ -105,9 +99,7 @@ You can search with [selectors](/reference/node-selection/methods). Below are th
 
 </VersionBlock>
 
-Because the results of selectors are immutable, the filter side panel is not available with this search method. 
-
-When searching with selector methods, you can also use [graph operators](/reference/node-selection/graph-operators). For example, `+orders` returns all the parents of `orders`. This functionality is not available for keyword search.
+When searching with selector methods, you can also use [graph operators](/reference/node-selection/graph-operators). For example, `+orders` returns all the upstream nodes of `orders` and `orders+1` returns just the nodes immediately downstream (the children) of `orders`.
 
 You can use multiple selector methods in your search query with [set operators](/reference/node-selection/set-operators). A space implies a union set operator and a comma for an intersection. For example:
 - `resource_type:metric,tag:nightly` &mdash; Returns metrics with the tag `nightly`

website/docs/docs/dbt-versions/release-notes/72-Feb-2024/job-completion-trigger.md

@@ -0,0 +1,18 @@
+---
+title: "New: Trigger on job completion"
+description: "February 2024: Native support now available in dbt Cloud for triggering deploy jobs when other deploy jobs finish."
+sidebar_label: "New: Trigger on job completion"
+sidebar_position: 07
+tags: [Feb-2024]
+date: 2024-02-15
+---
+
+# New: Trigger on job completion <Lifecycle status="team,enterprise" />
+
+Now available for dbt Cloud Team and Enterprise plans is the ability to trigger deploy jobs when other deploy jobs are complete. You can enable this feature [in the UI](/docs/deploy/deploy-jobs) with the  **Run when another job finishes** option in the **Triggers** section of your job or with the [Create Job API endpoint](/dbt-cloud/api-v2#/operations/Create%20Job). 
+
+When enabled, your job will run after the specified upstream job completes. You can configure which run status(es) will trigger your job. It can be just on `Success` or on all statuses. If you have dependencies between your dbt projects, this allows you to _natively_ orchestrate your jobs within dbt Cloud &mdash; no need to set up a third-party tool.
+
+An example of the **Triggers** section when creating the job:  
+
+<Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/example-triggers-section.png" width="90%" title="Example of Triggers on the Deploy Job page"/>

website/docs/docs/dbt-versions/release-notes/72-Feb-2024/keep-on-latest-version.md

@@ -2,7 +2,7 @@
 title: "New: Keep on latest version"
 description: "February 2024: New setting, called Keep on latest version, that allows dbt Labs to handle version upgrades for you."
 sidebar_label: "New: Keep on latest version"
-sidebar_position: 06
+sidebar_position: 08
 tags: [Feb-2024]
 date: 2024-02-14
 ---