are there any supported ways for minimizing a config map, similar to how ig/build uses (the private) ig/dependent-keys internally? We have a giant shared config across services (not my choice) and we pass a vector of keys to init to grab the tree we want. It would be nice to do this statically
you can pass only keys of top-level services required as a part of application. for example in case service A depends only on B and B depends only on C, C does not depend on anything. In the config you can define services A, B, C and D. Then calling init function with only A will starts A, B and C only.
Yes...i would like to produce that map statically so that every container does not get the whole map to prune services from. This is doable using private functions, id like to not use private functions
ok, but you still can use build for this
(select-keys config (keys (ig/build config [::a] (constantly nil))))