Optionally load provider config from /etc/opk/providers.d#108
Optionally load provider config from /etc/opk/providers.d#108markafarrell wants to merge 3 commits into
Conversation
1a01dc8 to
794241e
Compare
|
I don't want to complicate this further, but could we support a proper hierarchy of files? The UAPI group, a collection of linux distro, has a "Configuration Files Specification" that allows a hierarchy of files in which we could provide system defaults and overrides. I suspect it would be nice to implement this with https://uapi-group.org/specifications/specs/configuration_files_specification/ |
For the sake of not having to worry about upgrades, we should do this now. A good chunk of the code is the upcoming release will be around configuration files. This is exactly the right moment to get our ducks in a row. Can you open a PR or issue that proposes what changes we need to make? |
|
@EthanHeilman Did we want to try to support the current format and a new yaml based format? Or are we happy to just throw away the current format and only support a new yaml based format for provider configuration for future releases? |
|
@Foxboron @EthanHeilman I have created a new issue #115 to discuss the possible format for provider configuration |
794241e to
9338833
Compare
cc65b52 to
993c204
Compare
I'm still thinking about the yaml format. I don't think we can throw away the current format. |
Optionally load providers from
/etc/opk/providers.dFixes #107