Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating staging page #5884

Merged
merged 3 commits into from
Aug 2, 2024
Merged

Updating staging page #5884

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f6f662a
Updating staging page
matthewshaver Aug 2, 2024
acb911d
Update website/docs/docs/deploy/deploy-environments.md
matthewshaver Aug 2, 2024
6802a27
Update website/docs/docs/deploy/deploy-environments.md
matthewshaver Aug 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 2 additions & 5 deletions website/docs/docs/deploy/deploy-environments.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,13 +57,10 @@ Some customers prefer to connect Development and Staging to their `main` branch

### Why use a staging environment

There are two primary motivations for using a Staging environment:
There are three primary motivations for using a Staging environment:
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
1. An additional validation layer before changes are deployed into Production. You can deploy, test, and explore your dbt models in Staging.
2. Clear isolation between development workflows and production data. It enables developers to work in metadata-powered ways, using features like deferral and cross-project references, without accessing data in production deployments.

:::info Coming soon: environment-level permissions
Provide developers with the ability to create, edit, and trigger ad hoc jobs in the Staging environment, while keeping the Production environment locked down.
:::
3. Manage user access to production using [environment-level permissions](/docs/cloud/manage-access/environment-permissions).
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved

**Conditional configuration of sources** enables you to point to "prod" or "non-prod" source data, depending on the environment you're running in. For example, this source will point to `<DATABASE>.sensitive_source.table_with_pii`, where `<DATABASE>` is dynamically resolved based on an environment variable.

Expand Down
Loading