-
Notifications
You must be signed in to change notification settings - Fork 14
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
changes to tls-mode from default to prefer and update test cases #152
Changes from all commits
15e641c
2af7448
dc1bded
b4c002f
b300bfb
99eb543
7542304
274a03e
b44c59a
5b0077c
ec24054
61de288
4f3ec86
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,7 @@ | ||
//Should we remove this file as its a redundant test for TLS mode? | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it is reasonable to move this test for bad credentials to tls-tests.js. Additionally, I would be partial to not only moving this test into tls-tests.js, but also moving tls-tests.js into mochatest/integration/connection (currently only client directory exists so we would add connection). This is surely not any sort of requirement for this work so if you would prefer to leave things as they are, that is fine. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can open up another PR later for moving the tests and doing some more cleanup. |
||
//All TLS test suites for various TLS modes can be found at vertica-nodejs/test/integration/connection/tls-tests.js | ||
|
||
|
||
'use strict' | ||
|
||
const vertica = require('../../../lib') | ||
|
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.
For the management of our connection state events, 'sslconnect' is the proper event to emit. This may seem odd because we are not actually connecting with SSL wrapped socket in this case, however the sslconnect event just symbolizes that we completed our attempt at an ssl connection.
So this code and this emission of 'sslconnect' is correct. Just wanted to add some context