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
{{ message }}
This repository was archived by the owner on Mar 13, 2025. It is now read-only.
| PORT | The port the application will listen on | 3002 |
8
8
| LOG_LEVEL | The log level | info |
9
-
| MONGODB_URI | The MongoDB URI. This needs to be the same MongoDB used by topcoder-x-receiver, topcoder-x-processor, and topcoder-x-site | mongodb://127.0.0.1:27017/topcoderx |
10
9
|TOPIC | The Kafka topic where events are published. This must be the same as the configured value for topcoder-x-processor||
11
10
|KAFKA_OPTIONS | Kafka connection options||
12
-
|KAFKA_HOST| The Kafka host to connect to| localhost:9092 |
11
+
|KAFKA_URL| The Kafka host to connect to| localhost:9092 |
13
12
|KAFKA_CLIENT_CERT | The Kafka SSL certificate to use when connecting| Read from kafka_client.cer file, but this can be set as a string like it is on Heroku |
14
13
|KAFKA_CLIENT_CERT_KEY | The Kafka SSL certificate key to use when connecting| Read from kafka_client.key file, but this can be set as a string like it is on Heroku|
14
+
|AWS_ACCESS_KEY_ID | The Amazon certificate key to use when connecting. Use local dynamodb you can set fake value|FAKE_ACCESS_KEY_ID |
15
+
|AWS_SECRET_ACCESS_KEY | The Amazon certificate access key to use when connecting. Use local dynamodb you can set fake value|FAKE_SECRET_ACCESS_KEY |
16
+
|AWS_REGION | The Amazon certificate region to use when connecting. Use local dynamodb you can set fake value|FAKE_REGION |
17
+
|IS_LOCAL | Use Amazon DynamoDB Local or server | 'false' |
15
18
16
19
KAFKA_OPTIONS should be object as described in https://github.com/oleksiyk/kafka#ssl
17
20
For using with SSL, the options should be as
18
21
```
19
22
{
20
23
connectionString: '<server>',
21
24
ssl: {
22
-
cert: '<certificate>',
25
+
cert: '<certificate>',
23
26
key: '<key>'
24
27
}
25
28
}
@@ -39,7 +42,7 @@ Configure a Github project with a webhook with a format like this: https://<rece
39
42
#### Smoke test
40
43
- Create an issue in the repo, you can see the logs in `receiver`, the `issue.created` event is generated.
41
44
42
-
You can test other events, but just validating that an issue.created event is generated in Kafka is enough to smoke test the receiver is set up properly.
45
+
You can test other events, but just validating that an issue.created event is generated in Kafka is enough to smoke test the receiver is set up properly.
0 commit comments