Merge branch 'current' into dbeatty/access-method-in-v1.5

website/docs/docs/cloud/manage-access/enterprise-permissions.md

@@ -4,14 +4,9 @@ id: "enterprise-permissions"
 description: "Permission sets for Enterprise plans."
 ---
 
-:::info Enterprise Feature
+import SetUpPages from '/snippets/_available-enterprise-only.md';
 
-This guide describes a feature of the dbt Cloud Enterprise plan.
-If you're interested in learning more about an Enterprise plan, contact us at sales@getdbt.com.
-
-:::
-
-## Overview
+<SetUpPages features={'/snippets/_available-enterprise-only.md'}/>
 
 The dbt Cloud Enterprise plan supports a number of pre-built permission sets to
 help manage access controls within a dbt Cloud account. See the docs on [access

website/docs/docs/cloud/manage-access/set-up-sso-azure-active-directory.md

@@ -5,11 +5,9 @@ id: "set-up-sso-azure-active-directory"
 sidebar_label: "Set up SSO with Azure AD"
 ---
 
-:::info Enterprise Feature
-This guide describes a feature of the dbt Cloud Enterprise plan. If you’re
-interested in learning more about an Enterprise plan, contact us at
-sales@getdbt.com.
-:::
+import SetUpPages from '/snippets/_sso-docs-mt-available.md';
+
+<SetUpPages features={'/snippets/_sso-docs-mt-available.md'}/>
 
 dbt Cloud Enterprise supports single-sign on via Azure Active Directory (Azure AD).
 You will need permissions to create and manage a new Azure AD application.
@@ -171,4 +169,4 @@ Now you have completed setting up SSO with Azure AD, the next steps will be to s
 
 Ensure that the domain name under which user accounts exist in Azure matches the domain you supplied in [Supplying credentials](#supplying-credentials) when you configured SSO.
 
-<Lightbox collapsed="true" src="/img/docs/dbt-cloud/dbt-cloud-enterprise/azure/azure-get-domain.png" title="Obtaining the user domain from Azure" />
+<Lightbox collapsed="true" src="/img/docs/dbt-cloud/dbt-cloud-enterprise/azure/azure-get-domain.png" title="Obtaining the user domain from Azure" />

website/docs/docs/cloud/manage-access/set-up-sso-google-workspace.md

@@ -4,11 +4,9 @@ description: "Learn how dbt Cloud administrators can use Single-Sign On (SSO) vi
 id: "set-up-sso-google-workspace"
 ---
 
-:::info Enterprise Feature
-This guide describes a feature of the dbt Cloud Enterprise plan. If you’re
-interested in learning more about an Enterprise plan, contact us at
-sales@getdbt.com.
-:::
+import SetUpPages from '/snippets/_sso-docs-mt-available.md';
+
+<SetUpPages features={'/snippets/_sso-docs-mt-available.md'}/>
 
 dbt Cloud Enterprise supports Single-Sign On (SSO) via Google GSuite. You will need
 permissions to create and manage a new Google OAuth2 application, as well as

website/docs/docs/cloud/manage-access/set-up-sso-okta.md

@@ -3,11 +3,9 @@ title: "Set up SSO with Okta"
 id: "set-up-sso-okta"
 ---
 
-:::info Enterprise Feature
+import SetUpPages from '/snippets/_sso-docs-mt-available.md';
 
-This guide describes a feature of the dbt Cloud Enterprise plan. If you’re interested in learning more about an Enterprise plan, contact us at sales@getdbt.com.
-
-:::
+<SetUpPages features={'/snippets/_sso-docs-mt-available.md'}/>
 
 ## Okta SSO
 

website/docs/docs/cloud/manage-access/set-up-sso-saml-2.0.md

@@ -3,12 +3,9 @@ title: "Set up SSO with SAML 2.0"
 id: "set-up-sso-saml-2.0"
 ---
 
-:::info Enterprise Feature
+import SetUpPages from '/snippets/_sso-docs-mt-available.md';
 
-This guide describes a feature of the dbt Cloud Enterprise plan. If you’re interested in learning
-more about an Enterprise plan, contact us at sales@getdbt.com.
-
-:::
+<SetUpPages features={'/snippets/_sso-docs-mt-available.md'}/>
 
 dbt Cloud Enterprise supports single-sign on (SSO) for any SAML 2.0-compliant identity provider (IdP).
 Currently supported features include:

website/docs/docs/cloud/secure/ip-restrictions.md

@@ -1,11 +1,13 @@
 ---
 title: "Configuring IP restrictions"
 id: ip-restrictions
-description: "Configuring IP retrictions to outside traffic from accessing your dbt Cloud environment"
+description: "Configuring IP restrictions to outside traffic from accessing your dbt Cloud environment"
 sidebar_label: "IP restrictions"
 ---
 
-## About IP Restrictions
+import SetUpPages from '/snippets/_available-tiers-iprestrictions.md';
+
+<SetUpPages features={'/snippets/_available-tiers-iprestrictions.md'}/>
 
 IP Restrictions help control which IP addresses are allowed to connect to dbt Cloud. IP restrictions allow dbt Cloud customers to meet security and compliance controls by only allowing approved IPs to connect to their dbt Cloud environment. This feature is supported in all regions across NA, Europe, and Asia-Pacific, but contact us if you have questions about availability.
 
@@ -67,4 +69,4 @@ Once enabled, when someone attempts to access dbt Cloud from a restricted IP, th
 
 <Lightbox src="/img/docs/dbt-cloud/ip-restricted-email.png" title="IP restricted access denied message for email logins"/>
 
-<Lightbox src="/img/docs/dbt-cloud/ip-restricted-sso.png" title="IP restricted access denied message for SSO logins"/>
+<Lightbox src="/img/docs/dbt-cloud/ip-restricted-sso.png" title="IP restricted access denied message for SSO logins"/>

website/docs/faqs/Models/unique-model-names.md

@@ -6,6 +6,20 @@ id: unique-model-names
 
 ---
 
-Yes! To build dependencies between models, you need to use the `ref` function. The `ref` function only takes one argument — the model name (i.e. the filename). As a result, these model names need to be unique, _even if they are in distinct folders_.
+<VersionBlock firstVersion="1.6">
+
+Within one project: yes! To build dependencies between models, you need to use the `ref` function, and pass in the model name as an argument. dbt uses that model name to uniquely resolve the `ref` to a specific model. As a result, these model names need to be unique, _even if they are in distinct folders_.
+
+A model in one project can have the same name as a model in another project (installed as a dependency). dbt uses the project name to uniquely identify each model. We call this "namespacing." If you `ref` a model with a duplicated name, it will resolve to the model within the same namespace (package or project), or raise an error because of an ambiguous reference. Use [two-argument `ref`](/reference/dbt-jinja-functions/ref#two-argument-variant) to disambiguate references by specifying the namespace.
+
+Those models will still need to land in distinct locations in the data warehouse. Read the docs on [custom aliases](/docs/build/custom-aliases) and [custom schemas](/docs/build/custom-schemas) for details on how to achieve this.
+
+</VersionBlock>
+
+<VersionBlock lastVersion="1.5">
+
+Yes! To build dependencies between models, you need to use the `ref` function, and pass in the model name as an argument. dbt uses that model name to uniquely resolve the `ref` to a specific model. As a result, these model names need to be unique, _even if they are in distinct folders_.
 
 Often, this question comes up because users want to give two models the same name in their warehouse, splitting them across separate schemas (e.g. `stripe.users` and `app.users`). Checkout the docs on [custom aliases](/docs/build/custom-aliases) and [custom schemas](/docs/build/custom-schemas) to achieve this.
+
+</VersionBlock>

website/docs/guides/migration/versions/01-upgrading-to-v1.6.md

@@ -27,7 +27,7 @@ dbt Labs is committed to providing backward compatibility for all versions 1.x,
 
 ## New and changed documentation
 
-**Coming Soon**
+[**Namespacing:**](/faqs/Models/unique-model-names) Model names can be duplicated across different namespaces (packages/projects), so long as they are unique within each package/project. We strongly encourage using [two-argument `ref`](/reference/dbt-jinja-functions/ref#two-argument-variant) when referencing a model from a different package/project.
 
 ### Quick hits
 

website/docs/reference/dbt-jinja-functions/ref.md

@@ -73,13 +73,21 @@ select * from {{ ref('model_name') }}
 
 ### Two-argument variant
 
-There is also a two-argument variant of the `ref` function. With this variant, you can pass both a package name and model name to `ref` to avoid ambiguity. This functionality is not commonly required for typical dbt usage.
+There is also a two-argument variant of the `ref` function. With this variant, you can pass both a namespace (project or package) and model name to `ref` to avoid ambiguity.
 
 ```sql
-select * from {{ ref('package_name', 'model_name') }}
+select * from {{ ref('project_or_package', 'model_name') }}
 ```
 
-**Note:** The `package_name` should only include the name of the package, not the maintainer. For example, if you use the [`fivetran/stripe`](https://hub.getdbt.com/fivetran/stripe/latest/) package, type `stripe` in that argument, and not `fivetran/stripe`.
+We recommend using two-argument `ref` any time you are referencing a model defined in a different package or project. While not required in all cases, it's more explicit for you, for dbt, and for future readers of your code.
+
+<VersionBlock firstVersion="1.6">
+
+We especially recommend using two-argument `ref` to avoid ambiguity, in cases where a model name is duplicated across multiple projects or installed packages. If you use one-argument `ref` (just the `model_name`), dbt will look for a model by that name in the same namespace (package or project); if it finds none, it will raise an error.
+
+</VersionBlock>
+
+**Note:** The `project_or_package` should match the `name` of the project/package, as defined in its `dbt_project.yml`. This might be different from the name of the repository. It never includes the repository's organization name. For example, if you use the [`fivetran/stripe`](https://hub.getdbt.com/fivetran/stripe/latest/) package, the package name is `stripe`, not `fivetran/stripe`.
 
 ### Forcing Dependencies
 

website/docs/reference/resource-configs/snapshot_name.md

@@ -17,7 +17,7 @@ description: "Snapshot-name - Read this in-depth guide to learn about configurat
 
 The name of a snapshot, as defined in the `{% snapshot %}` block header. This name is used when selecting from a snapshot using the [`ref` function](/reference/dbt-jinja-functions/ref)
 
-This name must not conflict with any other snapshot names, or any model names.
+This name must not conflict with the name of any other "refable" resource (models, seeds, other snapshots) defined in this project or package.
 
 The name does not need to match the file name. As a result, snapshot filenames do not need to be unique.
 

website/snippets/_available-enterprise-only.md

@@ -0,0 +1,5 @@
+:::info Limited to Enterprise
+
+This feature is limited to the dbt Cloud Enterprise plan. If you're interested in learning more about an Enterprise plan, contact us at <sales@getdbt.com>.
+
+:::

website/snippets/_available-tiers-iprestrictions.md

@@ -0,0 +1,9 @@
+:::info Limited to certain Enterprise tiers
+
+Organizations can configure IP restrictions using the following dbt Cloud Enterprise tiers:
+ * Business Critical 
+ * Virtual Private
+
+To learn more about these tiers, contact us at <sales@getdbt.com>.
+
+:::

website/snippets/_sso-docs-mt-available.md

@@ -0,0 +1,7 @@
+:::info Enterprise feature
+
+This guide describes a feature of the dbt Cloud Enterprise plan. If you’re interested in learning more about an Enterprise plan, contact us at <sales@getdbt.com>.
+
+These SSO configuration documents apply to multi-tenant Enterprise deployments only. [Single-tenant](/docs/cloud/about-cloud/tenancy#single-tenant) Virtual Private users can [email dbt Cloud Support](mailto:support@getdbt.com) to set up or update their SSO configuration. 
+
+:::

website/snippets/cloud-feature-parity.md

@@ -4,11 +4,11 @@ The following table outlines which dbt Cloud features are supported on the diffe
 |-------------------------------|--------------|-----------------------|----------------------|
 | Scheduler                     | ✅           | ✅                     | ✅                   |  
 | Cloud IDE                     | ✅           | ✅                     | ✅                   |  
-| Audit logs                    | ✅           | ✅ (select customers)  | ❌                   |  
-| Discovery API                  | ✅           | ✅ (select customers)  | ❌                   | 
+| Audit logs                    | ✅           | ✅                     | ✅                   |  
+| Discovery API                 | ✅           | ✅ (select customers)  | ❌                   | 
 | Webhooks (Outbound)           | ✅           | ❌                     | ❌                   |
 | Continuous Integration, including Slim CI                       | ✅           | ✅                     | ✅                   | 
 | Semantic Layer                | ✅ (North America Only) | ❌          | ❌                   | 
-| IP Restrictions               | ❌           | ✅                     | ✅                   | 
+| IP Restrictions               | ✅           | ✅                     | ✅                   | 
 | PrivateLink egress            | ✅           | ✅                     | ✅                   | 
 | PrivateLink ingress           | ❌           | ✅                     | ✅                   | 

website/src/components/docCarousel/index.js

@@ -1,8 +1,9 @@
 import React from 'react';
 import { Swiper, SwiperSlide } from 'swiper/react';
 import 'swiper/css';
-import { Navigation } from 'swiper';
+import { Navigation, Pagination } from 'swiper';
 import 'swiper/css/navigation';
+import 'swiper/css/pagination';
 
 function DocCarousel({ slidesPerView = 3, children }) {
     if ( !children?.length > 0 ){      
@@ -21,8 +22,8 @@ function DocCarousel({ slidesPerView = 3, children }) {
                 slidesPerView={1}
                 effect="fade"
                 navigation
-                modules={[Navigation]}
-
+                modules={[Navigation, Pagination]}
+                pagination={{ clickable: true }}
                 breakpoints={{
                   640: {
                     slidesPerView: 2,

website/src/css/custom.css

@@ -1815,6 +1815,24 @@ section>h2:not(.resource-section) {
   font-weight: 800;
 }
 
+/* General Swiper Styles */
+.docswiper .swiper-pagination-bullet {
+  height: 10px;
+  width: 10px;
+}
+
+.docswiper .swiper-pagination-bullet.swiper-pagination-bullet-active {
+  background: var(--ifm-color-info);
+}
+
+[data-theme='dark'] .docswiper .swiper-pagination-bullet {
+  background: var(--color-off-white);
+}
+
+[data-theme='dark'] .docswiper .swiper-pagination-bullet.swiper-pagination-bullet-active {
+  background: var(--color-light-teal);
+}
+
 /* Community Home styles */
 .community-home section {
   margin: calc(5vh) auto calc(2vh);