What is recommended options to make the YAML definition modular?

[empeje]

I maintain an API gateway with a lot of APIs and with 100+ APIs plus multiple plugins each, I want to make the YAML definition of the API separate or modular so that I can organize the config for each project, but when I update it I'll update it in an atomic way (all the config).

I know one of the solutions is to use yq to preprocess all the YAML and merge it together before pipe it to the kongfig. Do you have any plan or idea how make it supported by default?

[albertux]

@empeje I recommend to split your yaml in groups/categories of apis, so konfig apply doesn't take to much, is not ideal but reduce the time of the operation.

[empeje]

Well, I have a use case where we use Kubernetes configMap to store the kongfig.yaml and then use Kubernetes job to apply it. We are having a huge single configMap to store everything, I wonder if its good to split them out into multiple configMap. Anyway, I think this issue is not really relevant since I already have multiple workarounds.

---

edit.

Thanks @albertux