Control Nats Connection Name via ENV var#145
Merged
Merged
Conversation
wallyqs
reviewed
Feb 23, 2018
Member
wallyqs
left a comment
wallyqs
left a comment
There was a problem hiding this comment.
Change itself LGTM, but seems there are some issues in the build, will take a look
wallyqs
approved these changes
Feb 23, 2018
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
2 participants
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.
In order to test our Datadog Integration with gnatsd - we need to be able to control the name of the connection from the
nats-subandnats-pubCLI tools. In keeping with the rest of the options, we've made that configurable via an ENV var.