3 ms·
So the idea is to define a component in a general language for great configurability, and then make it possible to consume / instantiate it with YAML. What if
by rocqua 4y ago
So the idea is to define a component in a general language for great configurability, and then make it possible to consume / instantiate it with YAML.
What if the way you wrote the component does not allow some sort of dynamic config you need through YAML. Now you are working in two separate files and two different languages trying to make a change. Things almost get worse when the writer of the component and the consumer of the component are different people. Either massive horrible cludges happen to the YAML, or a weird back and forth needs to happen.
- mst 4y agoThis is just a specific case of "what if the program I'm using doesn't have a config file option for X" though. I usually run into it with webserver config files where (in both apache and nginx) I have to do something moderately contorted to get the end result I had in mind, but in the end the general case is just another trade-off.
- jaxxstorm 4y agoThis isn't how Multi-Language components work. The components only expose the inputs and outputs needed to the downstream consumer, you never have to "work in two separate files"