Looking here it appears we were using the verify flag as a pure boolean.verify can also take in a path to a CA cert to verify connections with. I added a new argument --ca-path which now allows the user to pass in the path to a custom CA cert. --secure will still set a boolean True and will expect that the certs are installed via certifi or can be grabbed from a public set of certs (check docs for list).
Looking here it appears we were using the
verify
flag as a pure boolean.verify
can also take in a path to a CA cert to verify connections with. I added a new argument--ca-path
which now allows the user to pass in the path to a custom CA cert.--secure
will still set a booleanTrue
and will expect that the certs are installed viacertifi
or can be grabbed from a public set of certs (check docs for list).