Since the genesis service is not a RESTful service, we will have to verify that it is successfully running using Kafka consumer and a S3 Bucket lookup.
Kafka
The genesis service dynamically creates topics based on the metadata of the DaaSDocument that is consumes.
Let's see what topics it has created.
NOTE: You will want to run this in a new terminal.
Before the genesis service send copies of the DaaSDocument downstream to be provisioned, it first stored the original copy in the S3 bucket that was configured in the gensis.rs file.
// NOTE: Modify the Bucket name to match your bucket
// Credentials are read from the environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
pub const BUCKET_NAME: &'static str = "iapp-archconf-workshop";
To confirm that the DaaSDocument has been stored in the S3 bucket, run the following command.