Support for HTTPS

[greg0ire]

Proposal

I want to migrate from Algolia SDK v3 to v4. Before I do that, I have some tests I want to rewrite as integration tests, and for that I would like to use wiremock. Sadly, v3 of the SDK has a hardcoded scheme: https://github.com/algolia/algoliasearch-client-go/blob/f5812bc08d3410e974915e14ed162e68dc737167/algolia/transport/transport.go#L269

This means I must use https, or do the SDK migration and the tests migration at once (which is not a great practice).

I don't know if that is going to work with testcontainers Cloud, which we use in the CI, but I've seen that Wiremock can serve its traffic over HTTPS

Apparently, that's also supported by the docker container, through the https-port option or with an environment variable: https://wiremock.org/docs/standalone/docker/

It would be nice if wiremock-testcontainers-go exposed an option to achieve this. So far I have tried some workarounds that seem to work by using options, but now the wiremock client that I want to use to start a recording does not trust wiremock's self signed certificate, so it seems I have more stuff to figure out. I fear that the algolia client won't either.

References

No response

[oleg-nenashev]

To confirm, it would be a good addition

[greg0ire]

I've been able to alter the algolia http client so that it blindly does not check the certificate, and things work 🎉
For wiremock, I've stuck with the HTTP endpoint.
I realize that since I can customize the http client used by Algolia, I might be able write an implementation that replaces https:// with just http://. Something to explore if for some reason this does not work in the CI, but I'm confident it will. In any case, support for HTTPs could be useful in some situations like this one.