lablup / lablup/backend.ai

Include the source from which the configuration was loaded as part of the config metadata

Open
#4,642 0 comments 0 reactions 1 assignee Claimed by @jopemachine View on GitHub
Dominant language
Python
Stars
670
Forks
183
Avg merge
17h 7m
Merged PRs (30d)
358

Description

If the same configuration is repeated across multiple sources, it can be confusing to determine where the config originated from.

This is especially true for those who are not familiar with the priority order of the config loaders, making it even more confusing.

To prevent such issues, let's add metadata to each config and make sure the config loader loads this metadata along with the config itself.

For example, if a certain setting exists in both `manager.toml` and `etcd`, and the "from" field of that setting indicates `etcd`, it would clearly show that the setting was ultimately overridden by the value from `etcd`.

JIRA Issue: BA-1537

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.