Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
None
Description
With the introduction of Descriptors, there are now two ways to specify configurations - in a file and within the application code.
This raises the question of what happens if a configuration is specified in both ways with different values. I.e., what is the precedence if a configuration has been set using both the descriptor and in the configuration file.
Current implementation gives higher precedence to generated configurations than those provided in configuration files.
This proposal is to make it so that if configuration is present in both, the value in configuration files has higher precedence.
This has the advantage that operational configurations can be changed at runtime by updating configuration files and redeploying, instead of requiring a full build and deploy. This is the natural/expected behavior for configurations.
This has the disadvantage that the configuration value in code may not match what's being used at runtime, which may be confusing when debugging. This might be OK since the source of truth for final configuration is the running container's logs anyway (because of various config rewriting and generation stages).
Attachments
Issue Links
- links to
