• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

tarantool / tarantool / 19548746781
88%

Build:
DEFAULT BRANCH: master
Ran 20 Nov 2025 07:35PM UTC
Jobs 1
Files 514
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Nov 2025 07:21PM UTC coverage: 87.649% (+0.02%) from 87.63%
19548746781

push

github

sergepetrenko
config: introduce an `iproto.ssl` section

This patch introduces a new `iproto.ssl` configuration section that can
be used to configure SSL. Previously, SSL might be configured by
providing `params` section in URIs as mentioned in the documentation
[^1]. The problem is that these URIs have been straightforwardly taken
from the configuration and instances tried to use other instances SSL
private keys to connect to them for replication and when using some of
the builtin modules such as `experimental.connpool`. The details are
available within #12030.

This fix aims to fix this problem. It introduces a new section `ssl`
that basically contains all the information the instance will use to
auth to other instances when using SSL. It uses the schema that
resembles existing `config.etcd.ssl`. Using this SSL works as intended.
Example of the new config.

```yaml
storage-1:
  iproto:
    listen:
      - uri: localhost:3301
        params:
          transport: 'ssl'
    ssl:
      ca_file: './certs/rootCA.pem'
      ssl_cert: './certs/storage-1-crt.pem'
      ssl_key: './certs/storage-1-key.pem'
storage-2:
  iproto:
    listen:
      - uri: localhost:3302
        params:
          transport: 'ssl'
    ssl:
      ca_file: './certs/rootCA.pem'
      ssl_cert: './certs/storage-2-crt.pem'
      ssl_key: './certs/storage-2-key.pem'
```

This configuration makes `storage-1` use the `storage-1` key/cert to set
the IProto socket up and to connect to `storage-2`. And `storage-2` uses
the `storage-2` key/cert to set its socket and to connect to `storage-1`
as it is expected.

Note that the old `param` section is still available. It will overwrite
less explicit behavior of the `ssl` section in favor of the backward
compatibility. Also, the parameters are not supplied to the connections
not using `ssl` as transport.

Unfortunately, using old `param` section is not alerted yet since using
configuration alert system will be introduced later since it requires
some non-trivial ... (continued)

70145 of 118117 branches covered (59.39%)

105316 of 120157 relevant lines covered (87.65%)

1359078.1 hits per line

Uncovered Existing Lines

Lines Coverage ∆ File
1
95.21
-0.53% src/box/vy_range.c
1
94.99
-0.21% src/box/vy_read_iterator.c
1
96.3
-3.7% src/cpu_feature.c
1
96.1
-0.05% src/lib/salad/bps_tree.h
1
85.15
-0.99% src/lib/small/small/slab_arena.c
1
22.64
-0.02% src/lib/uri/uri_parser.c
2
91.29
0.42% src/box/box.cc
2
81.38
-0.6% src/lib/core/coio.c
2
92.93
-0.2% src/lib/core/fiber.c
3
92.57
0.0% src/box/vinyl.c
3
87.87
-0.14% src/box/vy_run.c
3
85.59
-0.27% src/box/xlog.c
3
97.26
-0.3% src/lib/msgpuck/msgpuck.h
4
93.31
-1.27% src/lib/swim/swim_io.c
6
97.28
-0.4% src/box/lua/net_box.c
Jobs
ID Job ID Ran Files Coverage
1 19548746781.1 20 Nov 2025 07:35PM UTC 514
87.65
GitHub Action Run
Source Files on build 19548746781
  • Tree
  • List 514
  • Changed 32
  • Source Changed 0
  • Coverage Changed 32
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • a54a406d on github
  • Prev Build on master (#19538920465)
  • Next Build on master (#19574978427)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc