Issue with configuration file to render the values from environment variables about kratos HOT 7 OPEN

🤖

Hey @akoserwal, great to see you back! 😊 Hope you've been doing awesome since our last chat.

The issue you're experiencing is due to the way the default resolver in Kratos handles environment variables. The default resolver only supports flat keys, meaning it can only resolve environment variables that correspond to top-level keys in the configuration. It doesn't support nested keys like "data.testDB.endpoint".

Here's a snippet of the default resolver code for reference:

o := options{
		decoder:  defaultDecoder,
		resolver: defaultResolver,
		merge: func(dst, src interface{}) error {
			return mergo.Map(dst, src, mergo.WithOverride)
		},
	}

If you want to override nested keys with environment variables, you would need to implement a custom resolver that supports this feature. This custom resolver should be able to parse the environment variable names into nested keys.

Unfortunately, without the implementation of the defaultResolver, I can't provide a specific code example on how to modify it to support nested keys. However, the general idea would be to split the environment variable name on a certain character (like underscore or dot) and use the resulting parts as nested keys.

You can find more information about the default resolver and its limitations in the Kratos repository.

I hope this helps clarify the issue. If you have any further questions, feel free to ask.

Sources

• config/config.go
• transport/grpc/resolver/direct/builder.go

from kratos.

Hi, @akoserwal,

I'm helping the Kratos team manage their backlog and am marking this issue as stale. From what I understand, the issue involves a configuration file not rendering values from environment variables as expected in Kratos version v2.7.2 and Go version 1.19-1.21 on Mac OS. The environment variable "TEST_ENDPOINT" is set in the config file, but it does not override the key value as "data.testDB.endpoint." The default resolver in Kratos only supports flat keys, not nested keys, and a custom resolver that supports this feature would need to be implemented. There is also a discussion about the correct format of placeholders and handling non-string types in the comments.

Could you please confirm if this issue is still relevant to the latest version of the Kratos repository? If it is, please let the Kratos team know by commenting on the issue. Otherwise, feel free to close the issue yourself, or the issue will be automatically closed in 7 days.

Thank you!

from kratos.

I think here is a bug. Consider to change "$TEST_ENDPOINT" to "${ENDPOINT}" to avoid this temporary.

I made a reproduce project at local. Some of key codes:

server:
  http:
    addr: "${ADDR}"

c := config.New(
	config.WithSource(
		env.NewSource("TEST_"),
		file.NewSource(flagconf),
	),
)
c.Load()

var bc conf.Bootstrap
c.Scan(&bc)

fmt.Println(bc.Server.Http.Addr)
fmt.Println(c.Value("ADDR").String())
fmt.Println(c.Value("server.http.addr").String())

After I execute export TEST_ADDR=0.0.0.0:8000, codes run properly(print "0.0.0.0:8000").

I guess there has some mistakes of the format of placeholder. The comment say that the correct format is "${key:default}".

from kratos.

It's a mistake of doc. kratos don't support "$key" format by default. I found this test:

from kratos.

Thanks, @kvii, for clarifying.

It works if the export TEST_ADDR=0.0.0.0:8000 and use fmt.Println(bc.Server.Http.Addr)

For boolean, I am getting

Error
panic: proto: (line 1:133): invalid value for bool type: "true"

data:
  test:
    endpoint: "${ENDPOINT}"
    useTLS: "${TLS:false}"

export TEST_TLS=true

from kratos.

Same issue at #1565. Unfortunately, non-string types are not supported in Scan because that will include more complexity. You can use c.Value("data.test.useTLS").Bool() to get the bool value explicitly. But I think this doesn't match your case.

from kratos.

Issue is still relevant, I have PR opened to fix this issue

from kratos.