You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-37Lines changed: 0 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,43 +84,6 @@ As a preview, you can do [things](https://docs.getdbt.com/reference/resource-pro
84
84
- Add images / project logos from the repo into descriptions.
85
85
- Use HTML in your description.
86
86
87
-
### Dune employees using the project developing locally
88
-
Follow instructions from [Databricks](https://docs.databricks.com/dev-tools/dbt.html) on how to set up dbt-core.
89
-
90
-
Use the dbt_local_development cluster on Arrakis-[Dev](https://dbc-4f40755f-e259.cloud.databricks.com/?o=2121725202597946#setting/clusters/0414-134107-y2lk5vai/configuration).
91
-
Look under Advanced Options and JDBC/ODBC to find host name, port, and HTTP Path. Use a schema with your name in it, ex `dbt_meghan`.
In dbt cloud, navigate to your profile on the right hand side and then credentials in the menu on the left. You'll need to add a personal access token to the spellbook dev project from generated from the arrakis-dev databricks workspace. You won't need to add credentials for spellbook prod.
110
-
111
-
<imgwidth="1428"alt="Screen Shot 2022-04-28 at 4 58 28 PM"src="https://user-images.githubusercontent.com/9472574/165844567-a02d11c7-3195-46c6-b80b-40de6cff7d79.png">
112
-
113
-
These credentials will be used for the Develop IDE in the hamburger menu. You can run dbt commands from this browser IDE and preview query results, lineages, and compiled SQL.
114
-
115
-
### Dune employees deploying the project
116
-
117
-
Each pull request triggers a PR job in dbt cloud spellbook dev. This job will run and test only the models that have been modified since the last dev deploy job which runs daily. Verify this job runs correctly and request code review from a colleague. When approved, merge into main.
118
-
119
-
When we are ready to deploy to production, merge main into a new branch named following the v{major}-{minor}-{patch} pattern. In dbt cloud spellbook prod deploy environment, update the custom branch to match the new branch (note the name of the current branch). Trigger the production deploy or production deploy full refresh job depending on whether the change needs to rewrite exisiting tables.
120
-
121
-
<imgwidth="1166"alt="Screen Shot 2022-04-28 at 5 29 08 PM"src="https://user-images.githubusercontent.com/9472574/165849010-64cd5306-d6ab-4514-813a-7496bc8591b7.png">
122
-
123
-
If the deploy fail, rollback by replacing the previous branch and trigger the job again.
0 commit comments