A unified configuration environment should be created upon startup that is created from cloud provider user data, local configuration files on the host, and possibly environmental data.
Part of this bug will be to ensure that the documentation clearly illustrates where the config can be loaded from and the order of precedence
We may or may not wish to support command line options, and also secrets from the secret store. The environmental data would be both environment variables, plus potentially querying cloud endpoints to get things like workerId which might not be in the user data.
Creating and loading a configuration has been solved.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.