cluter: force TLS for https:// endpoints - #1353
Merged
Merged
Conversation
sssciel
force-pushed
the
g.rybakov/tntp-8695-https-fix
branch
from
August 21, 2026 07:57
8065583 to
b525862
Compare
sssciel
changed the title
cluter: force TLS for https:// TCS/etcd endpoints without ssl params
sssciel
force-pushed
the
g.rybakov/tntp-8695-https-fix
branch
from
August 21, 2026 07:59
b525862 to
664e853
Compare
Mockird31
approved these changes
Aug 24, 2026
sssciel
force-pushed
the
g.rybakov/tntp-8695-https-fix
branch
from
August 28, 2026 08:28
664e853 to
c7832a7
Compare
tt cluster publish/show timed out when connecting to a Tarantool Config Storage or etcd endpoint over https:// with SSL enabled server-side but no client certificate required, since transport selection only looked at explicit ssl_* URI params, ignoring the scheme. UriOpts now carries Scheme, and ConnectTarantool/ConnectEtcd force a secure connection when it's "https". Closes TNTP-8695
sssciel
force-pushed
the
g.rybakov/tntp-8695-https-fix
branch
from
August 28, 2026 12:51
c7832a7 to
a489b20
Compare
bigbes
approved these changes
Aug 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
tt cluster publish/show timed out when connecting to a Tarantool Config Storage or etcd endpoint over https:// with SSL enabled server-side but no client certificate required, since transport selection only looked at explicit ssl_* URI params, ignoring the scheme. UriOpts now carries Scheme, and ConnectTarantool/ConnectEtcd force a secure connection when it's "https".
Closes TNTP-8695