Skip to content

Commit 6b61959

Browse files
committed
Addressed the errors shown in the workflows
1 parent 3e969ed commit 6b61959

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

quickstarts/manage-data/dagster-teradata-s3-to-teradata-transfer.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -187,20 +187,20 @@ Go to the **"Launchpad"** and provide the configuration for the **TeradataResour
187187
resources:
188188
s3:
189189
config:
190-
aws_access_key_id:
191-
aws_secret_access_key:
192-
aws_session_token:
190+
aws_access_key_id: <AWS_ACCESS_KEY_ID>
191+
aws_secret_access_key: <AWS_SECRET_ACCESS_KEY>
192+
aws_session_token: <AWS_SESSION_TOKEN>
193193
max_attempts: 5
194194
use_ssl: true
195195
use_unsigned_session: false
196196
teradata:
197197
config:
198-
database:
199-
host:
200-
password:
201-
user:
198+
host: <TERADATA_HOST>
199+
user: <TERADATA_USER>s
200+
password: <TERADATA_PASSWORD>
201+
database: <TERADATA_DATABASE>
202202
```
203-
Replace <AWS_ACCESS_KEY_ID>, <AWS_SECRET_ACCESS_KEY>, <AWS_SESSION_TOKEN>, <TERADATA_DATABASE>, <TERADATA_HOST>, <TERADATA_PASSWORD>, and <TERADATA_USER> with the actual values for your S3 and Teradata configuration.
203+
Replace `<AWS_ACCESS_KEY_ID>, <AWS_SECRET_ACCESS_KEY>, <AWS_SESSION_TOKEN>, <TERADATA_HOST>, <TERADATA_USER>, <TERADATA_PASSWORD>, and <TERADATA_DATABASE>` with the actual values for your S3 and Teradata configuration.
204204
Once the configuration is done, click on **"Launch Run"** to start the process.
205205
206206
![dagster-teradata-s33.png](../images/dagster/dagster-teradata-s33.png)

0 commit comments

Comments
 (0)