I'm still busy with the Hoplite 3 migration, now t...
# hoplite
s
I'm still busy with the Hoplite 3 migration, now testing version 3.0.1. Our test now break when it comes to verifying order of precedence WRT taking properties from different property sources. It seems that the environment source is simply ignored. Did anything change here, like the syntax of environment variable names?
s
There was a change in what was registered by default but in like 3.0 rc1 6 months ago. Is your issue only between 3 and 3.01?
s
No, the issue is going from 2.9.0 to 3.0.1. From q quick glance, it seems that github.com/sksamuel/hoplite/pull/414 is related. But just changing "__" or "." to "_" in env var names does not seem to solve the problem. I need to look deeper.
FYI, the assertion that fails is this. Env var values don't take precedence as expected anymore.
just changing "__" or "." to "_" in env var names does not seem to solve the problem
It does partly solve the problem, not sure what I did wrong earlier. However, there seem to be additional problem with casing, i.e when using uppercase env var names to override lower-case properties.
Also, invalid configuration does not seem to throw
ConfigException
anymore even if
DecodeMode.Strict
is set...
Ok, here's a bunch of more fixes: github.com/sksamuel/hoplite/pull/600
s
3.0.3 released
🚀 2
s
With this, I was finally able to upgrade ORT to from Hoplite 2.9.0 to 3.0.3 🎉
👍 1
s
Congrats!
😄 1