-
Notifications
You must be signed in to change notification settings - Fork 949
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
Ensure learners don't try to save a new file in main branch #4304
Changes from all commits
f8d196e
ee04d8b
fa72e99
0c105bc
a24dc9c
fc907eb
6e93a69
0da0ba9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -88,25 +88,22 @@ In order to let dbt connect to your warehouse, you'll need to generate a keyfile | |
4. Click **Upload a Service Account JSON File** in settings. | ||
5. Select the JSON file you downloaded in [Generate BigQuery credentials](#generate-bigquery-credentials) and dbt Cloud will fill in all the necessary fields. | ||
6. Click **Test Connection**. This verifies that dbt Cloud can access your BigQuery account. | ||
7. Click **Next** if the test succeeded. If it failed, you might need to go back and regenerate your BigQuery credentials. | ||
7. Click **Next** if the test succeeds. If it fails, you might need to go back and regenerate your BigQuery credentials. | ||
|
||
|
||
## Set up a dbt Cloud managed repository | ||
<Snippet path="tutorial-managed-repo" /> | ||
|
||
|
||
## Initialize your dbt project and start developing | ||
## Initialize your dbt project | ||
Now that you have a repository configured, you can initialize your project and start development in dbt Cloud: | ||
|
||
1. Click **Start developing in the IDE**. It might take a few minutes for your project to spin up for the first time as it establishes your git connection, clones your repo, and tests the connection to the warehouse. | ||
2. Above the file tree to the left, click **Initialize dbt project**. This builds out your folder structure with example models. | ||
3. Make your initial commit by clicking **Commit and sync**. Use the commit message `initial commit` and click **Commit**. This creates the first commit to your managed repo and allows you to open a branch where you can add new dbt code. | ||
4. You can now directly query data from your warehouse and execute `dbt run`. You can try this out now: | ||
- Click **+ Create new file**, add this query to the new file, and click **Save as** to save the new file: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Addressing the issue. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @anksu2024 Removing this might muddle the instructions. Would it be better to direct the customer to put this on a different branch? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I followed the instructions and the same thing we are doing in the next section. i.e. we create a new branch and our first model on the branch. Hence, it would be a redundant activity, and the learner's flow would become more streamlined with this change. As a learner myself, I struggled for some time with this. Hence, I thought of adding. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @matthewshaver : Following up on this. Thx. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @anksu2024 Thank you for that perspective. I agree with the changes, but we must make some more adjustments to this section due to removing the text. I'll merge directly here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nevermind! I see you added it, Thank you! |
||
```sql | ||
select * from `dbt-tutorial.jaffle_shop.customers` | ||
``` | ||
- In the command line bar at the bottom, enter `dbt run` and click **Enter**. You should see a `dbt run succeeded` message. | ||
- To confirm the success of the above command, navigate to the BigQuery Console and discover the newly created models. | ||
|
||
## Build your first model | ||
1. Under **Version Control** on the left, click **Create branch**. You can name it `add-customers-model`. You need to create a new branch since the main branch is set to read-only mode. | ||
|
@@ -174,7 +171,7 @@ select * from final | |
|
||
6. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run and see the three models. | ||
|
||
Later, you can connect your business intelligence (BI) tools to these views and tables so they only read cleaned up data rather than raw data in your BI tool. | ||
Later, you can connect your business intelligence (BI) tools to these views and tables so they only read cleaned-up data rather than raw data in your BI tool. | ||
matthewshaver marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
#### FAQs | ||
|
||
|
@@ -282,7 +279,7 @@ Later, you can connect your business intelligence (BI) tools to these views and | |
|
||
4. Execute `dbt run`. | ||
|
||
This time, when you performed a `dbt run`, separate views/tables were created for `stg_customers`, `stg_orders` and `customers`. dbt inferred the order to run these models. Because `customers` depends on `stg_customers` and `stg_orders`, dbt builds `customers` last. You do not need to explicitly define these dependencies. | ||
This time, when you performed a `dbt run`, separate views/tables were created for `stg_customers`, `stg_orders`, and `customers`. dbt inferred the order to run these models. Because `customers` depends on `stg_customers` and `stg_orders`, dbt builds `customers` last. You do not need to explicitly define these dependencies. | ||
matthewshaver marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
#### FAQs {#faq-2} | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing this from here because we are starting development next section onwards.
We are making this section straightforward to follow.