Feedback from starburst-blumbert

nghi-ly · nghi-ly · commit c8a23bb6eebc · 2023-03-29T15:32:12.000-07:00
diff --git a/website/docs/docs/cloud/connect-data-platform/connect-starburst-trino.md b/website/docs/docs/cloud/connect-data-platform/connect-starburst-trino.md
@@ -4,13 +4,13 @@ description: "Configure Starburst/Trino connection."
 sidebar_label: "Connect Starburst/Trino"
 ---
 
-The required fields for setting up a Starburst Enterprise, Starburst Galaxy, and Trino cluster:  
+The required fields for setting up a connection with Starburst Enterprise, Starburst Galaxy, and Trino cluster are:  
 
 | Field | Description | Examples |
 | --- | --- | --- |
 | **Host** | The hostname of your Starburst Enterprise, Starburst Galaxy, or Trino cluster.&nbsp;Don't include the HTTP protocol. | `mycluster.mydomain.com` |
 | **Port** | The port to connect to for your Starburst Enterprise, Starburst Galaxy or Trino cluster.&nbsp;By default, it's 443 for TLS enabled clusters. | `443` |
-| **User** | The username (of the account) to log in to your Starburst Enterprise, Starburst Galaxy, or Trino cluster.&nbsp;The user must have permissions to create and drop tables.&nbsp;When connecting to Starburst Galaxy clusters, you must include the role of the user as a suffix to the username (for example, `*/dbt_user`).<br/><br/>NOTE:&nbsp;When connecting to a Starburst Enterprise cluster with built-in access controls enabled, you will not be able to provide the role as a suffix to the username, so the default role for the provided username will be used. | For Starburst Enterprise or Trino: <br/> <ul><li>`user.name`</li><li>`user.name@mydomain.com`</li></ul><br/>For Starburst Galaxy:<br/> <ul><li>`user.name@mydomain.com/role`</li></ul> |
+| **User** | The username (of the account) to log in to your Starburst Enterprise, Starburst Galaxy, or Trino cluster.&nbsp;The user must have permissions to create and drop tables.&nbsp;When connecting to Starburst Galaxy clusters, you must include the role of the user as a suffix to the username.<br/><br/>When connecting to a Starburst Enterprise cluster with built-in access controls enabled, you will not be able to provide the role as a suffix to the username, so the default role for the provided username will be used instead. | Format for Starburst Enterprise or Trino: <br/> <ul><li>`user.name`</li><li>`user.name@mydomain.com`</li></ul><br/>Format for Starburst Galaxy:<br/> <ul><li>`user.name@mydomain.com/role`</li></ul> |
 | **Password** | The user's password. |   |
 | **Database** | The name of a catalog in your Starburst Enterprise, Starburst Galaxy, or Trino cluster.&nbsp;The user must have read/write access to this catalog.&nbsp;The selection you make doesn't limit the data you can access through dbt to the specified catalog in Starburst/Trino.&nbsp;It's only used for the initial connection to your cluster. | `my_postgres_catalog` |
 | **Schema** | The name of a schema in your Starburst Enterprise, Starburst Galaxy, or Trino cluster that exists within the specified catalog. The user must have read/write access to this schema.&nbsp;The selection you make doesn't limit the data you can access through dbt to the specified schema in Starburst/Trino.&nbsp;It's only used for the initial connection to your cluster. | `my_schema` |
diff --git a/website/docs/docs/quickstarts/dbt-cloud/starburst-galaxy-qs.md b/website/docs/docs/quickstarts/dbt-cloud/starburst-galaxy-qs.md
@@ -15,15 +15,16 @@ In this quickstart guide, you'll learn how to use dbt Cloud with [Starburst Gala
 - Add tests to your models.
 - Document your models.
 - Schedule a job to run.
+- Connect more data sources to Starburst Galaxy
 
 :::tip Public Preview 
-The Starburst (Trino) connection in dbt Cloud is currently available in Public Preview for multi-tenant dbt Cloud accounts. Preview features are stable and can be considered for production deployments, but there may still be some planned additions and modifications to product behavior before moving to General Availability. For details, you can learn more about [dbt Product lifecycles](/docs/dbt-versions/product-lifecycles). 
+The Starburst (Trino) connection in dbt Cloud is currently available in Public Preview for multi-tenant dbt Cloud accounts. Preview features are stable and can be considered for production deployments, but there might still be some planned additions and modifications to product behavior before moving to General Availability. For details, refer to [dbt Product lifecycles](/docs/dbt-versions/product-lifecycles). 
 :::
 
 
 ## Prerequisites 
 - You have a [dbt Cloud account](https://www.getdbt.com/signup/).
-- You have [a trial Starburst Galaxy account](https://www.starburst.io/platform/starburst-galaxy/). For details, refer to the [getting started guide](https://docs.starburst.io/starburst-galaxy/get-started.html) in the Starburst Galaxy docs.
+- You have a [Starburst Galaxy account](https://www.starburst.io/platform/starburst-galaxy/). If you don't, you can start a free trial. Refer to the [getting started guide](https://docs.starburst.io/starburst-galaxy/get-started.html) in the Starburst Galaxy docs for further setup details.
 - You have an AWS account with permissions to upload data to an S3 bucket.
 - For Amazon S3 authentication, you will need either an AWS access key and AWS secret key with access to the bucket, or you will need a cross account IAM role with access to the bucket. For details, refer to these Starburst Galaxy docs: 
     - [AWS access and secret key instructions](https://docs.starburst.io/starburst-galaxy/security/external-aws.html#aws-access-and-secret-key)
@@ -53,7 +54,7 @@ Using Starburst Galaxy, you can create tables and also transform them with dbt.
                 stripe-payments.csv (file)
     ```
 
-## Connect Starburst Galaxy to the Amazon S3 bucket
+## Connect Starburst Galaxy to the Amazon S3 bucket {#connect-to-s3-bucket}
 If your Starburst Galaxy instance is not already connected to your S3 bucket, you need to create a cluster, create a catalog that connects to the S3 bucket, associate the new catalog (your data source) to your new cluster, and configure privilege settings. 
 
 In addition to Amazon S3, Starburst Galaxy supports many other data sources. To learn more about them, you can refer to the [Catalogs overview](https://docs.starburst.io/starburst-galaxy/catalogs/index.html) in the Starburst Galaxy docs.  
@@ -176,19 +177,21 @@ To query the Jaffle Shop data with Starburst Galaxy, you need to create tables u
 
 ## Connect dbt Cloud to Starburst Galaxy 
 
-1. Log in to [Starburst Galaxy](https://galaxy.starburst.io/login).
-2. If you haven&rsquo;t already, set your account&rsquo;s role to dbt_user. Click your email address in the upper right corner, choose **Switch role** and select **dbt_user**.
+1. Make sure you are still logged in to [Starburst Galaxy](https://galaxy.starburst.io/login).
+2. If you haven&rsquo;t already, set your account&rsquo;s role to accountadmin. Click your email address in the upper right corner, choose **Switch role** and select **accountadmin**. 
+    
+    If this role is not listed for you, choose the role you selected in [Connect Starburst Galaxy to the Amazon S3 bucket](#connect-to-s3-bucket) when you added location privilege for your S3 bucket.
 3. Click **Clusters** on the left sidebar.
-4. Find your cluster in the **View clusters** table and click **Connection info**. Choose **dbt** from the **Select client** dropdown. Keep the **Connection information** modal open. You will use details from that model in dbt Cloud.
+4. Find your cluster in the **View clusters** table and click **Connection info**. Choose **dbt** from the **Select client** dropdown. Keep the **Connection information** modal open. You will use details from that modal in dbt Cloud.
 5. In another browser tab, log in to [dbt Cloud](https://cloud.getdbt.com/).
 6. Create a new project in dbt Cloud. From Account settings (using the gear menu in the top right corner), click **+ New Project**.
 7. Enter a project name and click **Continue**.
-8. Choose **Trino (Starburst)** as your connection and click **Next**.
+8. Choose **Starburst** as your connection and click **Next**.
 9. Enter the **Settings** for your new project:
     - **Host** &ndash; The **Host** value from the **Connection information** modal in your Starburst Galaxy tab.
     - **Port** &ndash; 443 (which is the default)
 10. Enter the **Development Credentials** for your new project:
-    - **User** &ndash; The **User** value from the **Connection information** modal in your Starburst Galaxy tab. Make sure to use the entire string, including the /dbt_user part. If you don&rsquo;t include it, your default role is used and that might not have the correct permissions for project development.
+    - **User** &ndash; The **User** value from the **Connection information** modal in your Starburst Galaxy tab. Make sure to use the entire string, including the account's role which is the `/` and all the characters that follow. If you don&rsquo;t include it, your default role is used and that might not have the correct permissions for project development.
     - **Password** &ndash; The password you use to log in to your Starburst Galaxy account.
     - **Database** &ndash; The Starburst catalog you want to save your data to (for example, when writing new tables).
     - Leave the remaining options as is. You can use their default values.

-Original file line number
+Diff line change
 sidebar_label: "Connect Starburst/Trino"
 ---
 -The required fields for setting up a Starburst Enterprise, Starburst Galaxy, and Trino cluster:
 +The required fields for setting up a connection with Starburst Enterprise, Starburst Galaxy, and Trino cluster are:
 | Field | Description | Examples |
 | --- | --- | --- |
 | **Host** | The hostname of your Starburst Enterprise, Starburst Galaxy, or Trino cluster. Don't include the HTTP protocol. | `mycluster.mydomain.com` |
 | **Port** | The port to connect to for your Starburst Enterprise, Starburst Galaxy or Trino cluster. By default, it's 443 for TLS enabled clusters. | `443` |
 -| **User** | The username (of the account) to log in to your Starburst Enterprise, Starburst Galaxy, or Trino cluster. The user must have permissions to create and drop tables. When connecting to Starburst Galaxy clusters, you must include the role of the user as a suffix to the username (for example, `*/dbt_user`).<br/><br/>NOTE: When connecting to a Starburst Enterprise cluster with built-in access controls enabled, you will not be able to provide the role as a suffix to the username, so the default role for the provided username will be used. | For Starburst Enterprise or Trino: <br/> <ul><li>`user.name`</li><li>`[email protected]`</li></ul><br/>For Starburst Galaxy:<br/> <ul><li>`[email protected]/role`</li></ul> |
 +| **User** | The username (of the account) to log in to your Starburst Enterprise, Starburst Galaxy, or Trino cluster. The user must have permissions to create and drop tables. When connecting to Starburst Galaxy clusters, you must include the role of the user as a suffix to the username.<br/><br/>When connecting to a Starburst Enterprise cluster with built-in access controls enabled, you will not be able to provide the role as a suffix to the username, so the default role for the provided username will be used instead. | Format for Starburst Enterprise or Trino: <br/> <ul><li>`user.name`</li><li>`[email protected]`</li></ul><br/>Format for Starburst Galaxy:<br/> <ul><li>`[email protected]/role`</li></ul> |
 | **Password** | The user's password. |   |
 | **Database** | The name of a catalog in your Starburst Enterprise, Starburst Galaxy, or Trino cluster. The user must have read/write access to this catalog. The selection you make doesn't limit the data you can access through dbt to the specified catalog in Starburst/Trino. It's only used for the initial connection to your cluster. | `my_postgres_catalog` |
 | **Schema** | The name of a schema in your Starburst Enterprise, Starburst Galaxy, or Trino cluster that exists within the specified catalog. The user must have read/write access to this schema. The selection you make doesn't limit the data you can access through dbt to the specified schema in Starburst/Trino. It's only used for the initial connection to your cluster. | `my_schema` |