3 ms·
Never seen this problem in the wild. Seems like it would be a very rare issue limited to very large configs with conflicting names.
by grey-area 2mo ago
Never seen this problem in the wild. Seems like it would be a very rare issue limited to very large configs with conflicting names.
- thaumasiotes 2mo agoYou've never seen software that will use a default value, instead of refusing to operate, when a particular environment variable isn't present in the environment?
- grey-area 2mo agoNo I’ve never seen software that broke because someone added a config key.
- thaumasiotes 2mo agoAre you talking about altering environment variables in a system, or altering software to read different environment variables? I read jt2190 as talking about the former.
- grey-area 1mo agoI don’t use env variables for this and many other reasons. They seem like a spectacularly bad idea for config, as the op noted. I’m talking about altering a config which you control - adding to a config is pretty risk free if it is your program, altering a config of course is not.
- KnightHawk3 2mo agoI was deploying some dotnet app and it broke because the devs baked a config key into the image that was otherwise unset, which enabled it trying to start a SSL endpoint without a cert, thus breaking the app.