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
1. Change directory to the location of the centralized log group terraform:
228
+
229
+
```
230
+
cd unity-initiator/terraform-unity/centralized_log_group/
231
+
```
232
+
233
+
1. Set up environment variables for `project` (by default `uod`) and venue (by default `dev`):
234
+
235
+
```
236
+
export PROJECT=<your project, e.g. uod>
237
+
export VENUE=<your venue, e.g. dev>
238
+
```
239
+
240
+
1. Initialize terraform:
241
+
242
+
```
243
+
terraform init
244
+
```
245
+
246
+
1. Run terraform apply:
247
+
248
+
```
249
+
terraform apply \
250
+
--var project=${PROJECT} \
251
+
--var venue=${VENUE} \
252
+
-auto-approve
253
+
```
254
+
255
+
**Take note of the `centralized_log_group_name` that is output by terraform. It will be used when setting up other resources (e.g. initiator, trigger and evaluator lambdas).**
256
+
257
+
1. Export the `centralized_log_group_name` that was output from the centralized log group terraform deployment:
258
+
259
+
```
260
+
export CENTRALIZED_LOG_GROUP=<your log group name, e.g. /unity/log/uod-dev-initiator-centralized-log-group>
261
+
```
262
+
263
+
#### Deploying the Initiator
264
+
227
265
1. Change directory to the location of the inititator terraform:
228
266
229
267
```
230
-
cd unity-initiator/terraform-unity/initiator/
268
+
cd ../initiator/
231
269
```
232
270
233
271
1. You will need an S3 bucket for terraform to stage the router Lambda zip file and router configuration YAML file during deployment. Create one or reuse an existing one and set an environment variable for it:
@@ -248,12 +286,6 @@ This guide provides a quick way to get started with our project. Please see our
**Take note of the `initiator_topic_arn` that is output by terraform. It will be used when setting up any triggers.**
274
307
308
+
1. Export the `initiator_topic_arn` that was output from the initiator terraform deployment:
309
+
310
+
```
311
+
export INITIATOR_TOPIC_ARN=<initiator topic ARN>
312
+
```
313
+
275
314
#### Deploying Example Evaluators (SNS topic->SQS queue->Lambda)
276
315
277
316
In this demo we will deploy 2 evaluators:
@@ -320,6 +359,8 @@ In this demo we will deploy 2 evaluators:
320
359
321
360
```
322
361
terraform apply \
362
+
--var project=${PROJECT} \
363
+
--var venue=${VENUE} \
323
364
--var evaluator_name=${EVALUATOR_NAME} \
324
365
--var code_bucket=${CODE_BUCKET} \
325
366
-auto-approve
@@ -361,6 +402,8 @@ In this demo we will deploy 2 evaluators:
361
402
1. Run terraform apply:
362
403
```
363
404
terraform apply \
405
+
--var project=${PROJECT} \
406
+
--var venue=${VENUE} \
364
407
--var evaluator_name=${EVALUATOR_NAME} \
365
408
--var code_bucket=${CODE_BUCKET} \
366
409
-auto-approve
@@ -448,11 +491,12 @@ In this demo we will deploy 2 evaluators:
448
491
terraform init
449
492
```
450
493
451
-
1. Run terraform apply. Note the PROJECT and INITIATOR_TOPIC_ARN environment variables should have been set in the previous steps. If not set them again:
494
+
1. Run terraform apply. Note the PROJECT, VENUE and INITIATOR_TOPIC_ARN environment variables should have been set in the previous steps. If not set them again:
0 commit comments