-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dockerizing the bootstrapper app #160
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@walisc looks good to me. There is one typo; please fix it and we are good to merge.
String dbName = schemaDetails.dbName(); | ||
String dbSchemaFilePath = schemaDetails.schemaFilePath(); | ||
|
||
LOGGER.info(String.format("---> Create schama for database %s", dbName)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo here @walisc: schema
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ajinkyagadewar . Have update this 👍🏽 . Thanks!
Ticket: JMPI-771
Other Related Tickets: N/A
Other Related PRS: N/A
Describe of changes
This change dockerizes the current bootstrapper, allowing it to be part of the deployed stack/ a service in the swarm. This allows it to have access to the backend services deployed in the swarm for data management, primarily kafka, postgres, and dgraph.
Please note
devops/linux/docker/helper/scripts/d-stack-up-hub-containers.sh
devops/linux/docker/helper/bootstrapper/bootstrapper-docker.sh
). You can use this to call the bootstrapper methods, for example./helper/bootstrapper/bootstrapper-docker.sh data resetAll
How to test / configure