In the knowledge sharing session on LocalConfig
, there was a bit of confusion about some of the API methods of the gem.
The audience expected LocalConfig::Store#load_namespace!
to load configs from kubernetes, which it doesn't actually do. It merely loads a hash into memory. LocalConfig.load_namespaces!
on the other hand actually does load configmaps. But it additionally initializes the namespaces (including app
, which is not a kubernetes configmap).
Also, the boundaries between namespaces that build on shared kubernetes configmaps, namespaces that are just local objects are hard to grasp.
Furthermore, we might want to distinguish clearly between custom namespaces the app explicitly registers and namespaces that are pre-populated by the gem.
I came up with a proposal in https://github.com/local-ch/local_config/pull/19, which has yet to be confirmed if it's less confusing or not. Maybe it's easier to decide once people start working with it. The g