-
Notifications
You must be signed in to change notification settings - Fork 656
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
Pend invalid brats test (external db tls) #2567
Conversation
98343fd
to
982f577
Compare
This branch seems to have a lot more than just pending the brats test - is that intentional? |
Yeah, I suppose that could be split out The first set of commits were exploratory for understanding the problem (and adding some facilities for debugging this sort of thing in the future). I am/was hesitant to simply pend the specs without supporting info/evidence. That being said there are 3-4 commits which are purely cleanup that could likely be pushed separately. ¯_(ツ)_/¯ I collapsed some of the Golang fixups for clarity. |
55c031b
to
0bec3a0
Compare
Previously the brats tests were running against MySQL 5.7. Per the mysql2 docs the `sslverify` option is not supported as of MySQL 8.0 so this option is removed from the DB configuration.
This can be helpful for debugging / manually runnings specs.
- use camelCase - rename variable for clarity (golang) - remove unnecessary conversion (golang) - remove unused var (golang) - extract `var`'s rather than defining in each context (golang) - brats spec contexts use consistent order
- brats utils uses common SQL connection logic - remove whitespace from gcp_mysql.yml
This matches BOSH's expectations that the values be file names and not the file contents in the deployment manifest.
These tests have been invalid since their creation. From the beginning they have passed certificate material in the director deployment manifest, however the director itself has (always?) expected to be passed _paths_ to the certificates. Original tests here: f97c556#diff-ab90421945d114536b0c024f3cbaee7f4566c79a592ba9d46b395f0771745b42R293-R306 and Director config here: https://github.com/cloudfoundry/bosh/blob/c095b06c91f14ef51b5a8bcea20c3ec3651590b8/src/bosh-director/lib/bosh/director/config.rb#L303-L318
0bec3a0
to
886008e
Compare
These tests have been invalid since their creation. From the beginning they have passed certificate material in the director deployment manifest, however the director itself has (always?) expected to be passed paths to the certificates.
Original tests here:
f97c556#diff-ab90421945d114536b0c024f3cbaee7f4566c79a592ba9d46b395f0771745b42R293-R306
and
Director config here:
bosh/src/bosh-director/lib/bosh/director/config.rb
Lines 303 to 318 in c095b06