Conversation
Signed-off-by: shnacke <93600681+miazn@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wanted an easy way to call my new kafka producer in isolation from snarkOS, so decided to create a new cli command.
This works by adding a dir to the existing cli folder and allowing the message to be inserted in cli arguments. Note that you need to run
docker-compose upfor this to work.Also you need to declare the topic names ahead of time (harder to declare using the rust script itself). The way we might do this on the node is to write an
envsubstscript for thedocker-composefile itself on node startup.Also note that these kafka brokers are not encrypted, should add before pushing to node