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

Guidance on using clone command in dbt Cloud #3854

Open
1 task done
jtcohen6 opened this issue Aug 3, 2023 · 1 comment
Open
1 task done

Guidance on using clone command in dbt Cloud #3854

jtcohen6 opened this issue Aug 3, 2023 · 1 comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear

Comments

@jtcohen6
Copy link
Collaborator

jtcohen6 commented Aug 3, 2023

Contributions

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

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

At minimum:

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

I would want to use dbt clone in Cloud to:

  • create a "full" schema in development or CI, instead of deferring
  • (potentially) manage blue/green deploys (staging → production), on data platforms that support zero-copy cloning

In order to do that, I would create a job (CI / ad hoc) that defers to a job in my production environment.

Additional information

No response

@jtcohen6 jtcohen6 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels Aug 3, 2023
@jtcohen6 jtcohen6 added this to the dbt Core v1.6 Documentation milestone Aug 3, 2023
@matthewshaver
Copy link
Contributor

@jtcohen6 if I were to link to this best practice guide (we just recently created) on the pages you've mentioned here, would that satisfy the conditions or would we still need to add additional information?

@matthewshaver matthewshaver removed this from the dbt Core v1.6 Documentation milestone May 24, 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

2 participants