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.

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

How to set up staging envs procedures #5426

Open
1 task
runleonarun opened this issue May 1, 2024 · 0 comments
Open
1 task

How to set up staging envs procedures #5426

runleonarun opened this issue May 1, 2024 · 0 comments
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear

Comments

@runleonarun
Copy link
Collaborator

runleonarun commented May 1, 2024

Contributions

We should add more context and possibly these two procedures somewhere. One exists in paragraph form on the environments page, but maybe they both should become procedures?

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

docs.getdbt.com/docs/deploy/deploy-environments

What part(s) of the page would you like to see updated?

From initial customer beta feedback, I think there are two legitimate patterns:

  1. Production = default branch (main)
    • point Development + Staging to staging branch
    • point Production to main
    • promote to Production by merging from staging -> main
  2. Staging = default branch (main)
    • point Development + Staging to main branch
    • promote to Production by cutting "release" branches/tags off main at a regular interval (daily, weekly)
    • update Production environment (via dbt Cloud Admin API) to point to latest "release" branch/tag

Right now we've documented (1) here. I don't want to add too much complexity here, but we should mention that it's not the only legitimate/supported pattern.

Additional information

#5356 (comment)

@runleonarun runleonarun added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear
Projects
None yet
Development

No branches or pull requests

1 participant