Skip to content

Env-driven config for the new format is giving errors #1916

Description

@Atlas1225

Hello, I am migrating the config from iii-config.yaml to data/configuration with ${ENV} placeholders and pushing those as expected from version 0.16.7 (included). Env-driven config works for string fields (host, service_name, etc..). But it fails for typed fields, in my case, it fails for "port" field. Maybe there is a bug in this new config structure with environment-driven pattern:
invalid type: string "8080", expected u16 → engine drops the value, falls back to defaults
basically I set port: ${HTTP_PORT:3111} in data/configuration

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No fields configured for Bug.

Projects

Status
In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions