Skip to content
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

Fixed failed configuration reload due to present of leafnode with TLS #981

Merged
merged 1 commit into from May 2, 2019

Conversation

kozlovic
Copy link
Member

@kozlovic kozlovic commented May 2, 2019

We don't support reload of leafnode config yet, but we need to make
sure it does not fail the reload process if nothing has been changed.
(it would fail because TLSConfig internally do change in some cases)

Signed-off-by: Ivan Kozlovic ivan@synadia.com

We don't support reload of leafnode config yet, but we need to make
sure it does not fail the reload process if nothing has been changed.
(it would fail because TLSConfig internally do change in some cases)

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
Copy link
Member

@derekcollison derekcollison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@coveralls
Copy link

Coverage Status

Coverage increased (+0.04%) to 90.814% when pulling 5e01570 on fix_config_reload_leafnode_issue into 220330d on master.

@kozlovic kozlovic removed the request for review from wallyqs May 2, 2019 22:07
@kozlovic kozlovic merged commit 74c71f9 into master May 2, 2019
@kozlovic kozlovic deleted the fix_config_reload_leafnode_issue branch May 2, 2019 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants