Arvados

6432-pysdk-more-ca-certs-wip is up for review.

I thought about whether it made any sense to write a test, and ultimately decided against it. The point of the function is to introspect and report on the current state of the system. The only way to ensure that the results are wholly correct is to do the same introspection and assert that the function returned the expected result.

I thought about writing a test like, "Check if we're on Debian or Red Hat, or one of its derivatives. If so, assert that the result does not equal httplib2.CA_CERTS. Otherwise, assert that it does equal httplib2.CA_CERTS." However, this seemed only marginally better than the above approach.

What we really care about is that we can verify the cert of the API server we're connecting to, like Curoverse Cloud clusters. That's ultimately a system deployment question rather than a code question, so QA needs to be handled at that level, I think.

reviewing 6432-pysdk-more-ca-certs-wip at 798218c8505a784877251e2424d39c8204895e20

Code looks good, tests pass, LGTM.