Merge branch 'current' into add-export-all

website/docs/faqs/Git/github-permissions.md

@@ -6,29 +6,41 @@ sidebar_label: "GitHub and dbt Cloud permissions error"
 
 If you see the error `This account needs to accept the latest permissions for the dbt Cloud GitHub App` in dbt Cloud — this usually occurs when the permissions for the dbt Cloud GitHub App are out of date.
 
-To solve this issue, you'll need to update the permissions for the dbt Cloud GitHub App in your GitHub account. Here's a couple of ways you can do it:
+To solve this issue, you'll need to update the permissions for the dbt Cloud GitHub App in your GitHub account. This FAQ shares a couple of ways you can do it.
 
-#### Update permissions
+## Update permissions
 
-A Github organization admin will need to update the permissions in GitHub for the dbt Cloud GitHub App. If you're not the admin, reach out to your organization admin to request this. Alternatively, try [disconecting your GitHub account](#disconect-github) in dbt Cloud.
+A GitHub organization admin will need to update the permissions in GitHub for the dbt Cloud GitHub App. If you're not the admin, reach out to your organization admin to request this. 
+
+1. Navigate to your GitHub account. Click on the top right profile icon and then **Settings** (or personal if using a non-organization account).
+
+<Lightbox src="/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/github-settings.jpg" width="50%" title="Navigate to your GitHub account to configure your settings." />
+
+2. Then go to **Integrations** and then select **Applications** to identify any necessary permission changes. Note that a GitHub repository admin may not see the same permission request.
+
+<Lightbox src="/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/github-applications.jpg" width="80%" title="Navigate to Application settings to identify permission changes." />
+
+3. Click on **Review request** and then click on the **Accept new permissions** button on the next page.
+
+<Lightbox src="/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/github-review-request.jpg" width="80%" title="Grant access to the dbt Cloud app by accepting the new permissions." />
 
-1. Go directly to GitHub to determine if any updated permissions are required.
-2. In GitHub, go to your organization **Settings** (or personal if using a non-organization account).
-3. Then navigate to **Applications** to identify any necessary permission changes.
 For more info on GitHub permissions, refer to [access permissions](https://docs.github.com/en/get-started/learning-about-github/access-permissions-on-github).
 
-#### Disconnect GitHub
+Alternatively, try [disconecting your GitHub account](#disconect-github) in dbt Cloud, detailed in the following section.
+
+## Disconnect GitHub
 
 Disconnect the GitHub and dbt Cloud integration in dbt Cloud.
 
 1. In dbt Cloud, go to **Account Settings**.
-2. In **Projects**, select the project that's experiencing the issue.
+2. In **Projects**, select the project experiencing the issue.
 3. Click the repository link under **Repository**.
 4. In the **Repository details** page, click **Edit**.
 5. Click **Disconnect** to remove the GitHub integration.
-6. Go back to your **Project details** page and reconnect your repository by clicking the **Configure Repository** link.
+6. Return to your **Project details** page and reconnect your repository by clicking the **Configure Repository** link.
 7. Configure your repository and click **Save**
 
-<Lightbox src="/img/repository-details-faq.jpg" title="Disconnect your GitHub connection in the 'Repository details' page."/>
+<Lightbox src="/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/repository-details-faq.jpg" title="Disconnect your GitHub connection in the 'Repository details' page."/>
 
+## Support
 If you've tried these workarounds and are still experiencing this behavior &mdash; reach out to the [dbt Support](mailto:[email protected]) team and we'll be happy to help!

website/docs/guides/core-cloud-2.md

@@ -35,7 +35,7 @@ The guide outlines the following steps:
 
 ## Considerations
 
-If your team has is using dbt Core today, you could be reading this guide because:
+If your team is using dbt Core today, you could be reading this guide because:
 - You’ve realized the burden of maintaining that deployment.
 - The person who set it up has since left.
 - You’re interested in what dbt Cloud could do to better manage the complexity of your dbt deployment, democratize access to more contributors, or improve security and governance practices.
@@ -46,13 +46,13 @@ The most important things you need to think about when moving from dbt Core to d
 
 - How is your team structured? Are there natural divisions of domain?
 - Should you have one project or multiple? Which dbt resources do you want to standardize & keep central?
-- Who should have permissions to view, develop, administer?
+- Who should have permission to view, develop, and administer?
 - How are you scheduling your dbt models to run in production?
 - How are you currently managing Continuous integration/Continuous deployment (CI/CD) of logical changes (if at all)?
 - How do your data developers prefer to work?
 - How do you manage different data environments and the different behaviors in those environments?
 
-dbt Cloud provides standard mechanisms for tackling these considerations, all of which delivers long-term benefits to your organization:
+dbt Cloud provides standard mechanisms for tackling these considerations, all of which deliver long-term benefits to your organization:
 - Cross-team collaboration
 - Access control
 - Orchestration

website/docs/reference/dbt-jinja-functions/properties-yml-context.md

@@ -0,0 +1,34 @@
+---
+title: " About properties.yml context"
+sidebar_label: "properties.yml context"
+id: "dbt-properties-yml-context"
+description: "The context methods and variables available when configuring resources in a properties.yml file."
+---
+
+The following context methods and variables are available when configuring
+resources in a `properties.yml` file.
+
+**Available context methods:**
+- [env_var](/reference/dbt-jinja-functions/env_var)
+- [var](/reference/dbt-jinja-functions/var)
+
+**Available context variables:**
+- [target](/reference/dbt-jinja-functions/target)
+- [builtins](/reference/dbt-jinja-functions/builtins)
+- [dbt_version](/reference/dbt-jinja-functions/dbt_version)
+
+### Example configuration
+
+<File name='properties.yml'>
+
+```yml
+# Configure this model to be materialized as a view
+# in development and a table in production/CI contexts
+
+models:
+  - name: dim_customers
+    config:
+      materialized: "{{ 'view' if target.name == 'dev' else 'table' }}"
+```
+
+</File>