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

tarantool / go-config / 41535390632
84%
master: 84%

Build:
Build:
LAST BUILD BRANCH: bigbes/gh-no-demo-fixes
DEFAULT BRANCH: master
Ran 02 Nov 2026 10:15PM UTC
Jobs 1
Files 58
Run time 1min
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

02 Nov 2026 10:12PM UTC coverage: 83.795% (+0.7%) from 83.066%
41535390632

Pull #106

github

buyemune-sys
tarantool: read env values as the type of their path

The builder stores every TT_* value as a string. tt reads
config/etcd/endpoints with Get and expects a list: with
TT_CONFIG_ETCD_ENDPOINTS=http://127.0.0.1:2379 it gets a string,
decides there is no etcd and shows the file, while Tarantool uses etcd.
Validation fails the same value with "Value is string but should be
array", and so does TT_IPROTO_LISTEN='[{"uri":"127.0.0.1:3301"}]'.
Tarantool's env source reads the value by the schema type of its path.

With a schema, the builder now collects the env vars with schemaEnv, a
collector of its own: it resolves a name through the schema trie and
reads the value with the type the trie gives the path, by Tarantool's
rules (see the previous commit). The value goes into the config tree
typed, not only into the validation copy, so Get, Effective, merging
and validation see what a file would give them. An array or a map
becomes nodes, as the YAML collector builds them: an env array
replaces a file array whole instead of merging by index, and an env
map merges into a file map key by key, as Tarantool merges maps. A
string the schema made a string, JSON strings included, has a fixed
type, so TT_CONSOLE_SOCKET=123 stays "123" through the validator's
scalar coercion.

An empty value is dropped. Tarantool's fromenv returns nil for it and
the env source sets nothing, so TT_FOO= neither sets nor overrides a
file value there; storing "" would override the file and fail every
non-string field.

A value that cannot be read as its type (a record such as TT_CONSOLE,
JSON that does not parse, "yes" for a boolean) stays the raw string,
with no fixed type. Tarantool refuses to start on it, but tt reads
configs best-effort for status, stop and logs, so this is not an error
here; validation reports the type error as before.

A dedicated collector keeps the public API as it is. Doing it in
collectors.Env would need a value transform that returns subtrees with
fixed-type marks,... (continued)
Pull Request #106: tarantool: read env values as the type of their path

539 of 581 new or added lines in 5 files covered. (92.77%)

1 existing line in 1 file now uncovered.

6014 of 7177 relevant lines covered (83.8%)

1051.06 hits per line

Uncovered Changes

Lines Coverage ∆ File
16
87.79
tarantool/internal/envpath/types.go
11
90.52
tarantool/env.go
10
95.97
tarantool/internal/envpath/parse.go
5
88.19
1.27% tarantool/internal/envpath/envpath.go

Coverage Regressions

Lines Coverage ∆ File
1
88.19
1.27% tarantool/internal/envpath/envpath.go
Jobs
ID Job ID Ran Files Coverage
1 41535390632.1 02 Nov 2026 10:15PM UTC 58
83.8
GitHub Action Run
Source Files on build 41535390632
  • Tree
  • List 58
  • Changed 3
  • Source Changed 0
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #106
  • PR Base - master (#38212519261)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc