| > I like the idea of automatic proposed changes triggered by external events, but I'm not sure a monolithic tool with plugins is the best way of going about it. The Unix way to solve this problem would be to decompose your program into a couple of different programs that just do one thing, with flexible inputs and outputs. Waow, thanks a lot for you feedback, especially to take the time to write this down.
I'll do my best to answer as you cover different topics which have been scratching my head since the beginning of the project.
But first keep in mind that I had a strong constrain which was my spare time :). It's definitely something which I am planning to improve. Currently everything is done at build time and rely on Golang interface.
So a resource kind need to match a golang package. A package needs to implement the correct function for it to work.
for example for a "source" you need to implement the "source" function as in the following example. ```
func (m *Maven) Source(workingDir string) (string, error) {
// Implement whatever you need and return the source value
return "the source value", "an error if needed"
}
```
Like in this package https://github.com/updatecli/updatecli/tree/main/pkg/plugins... And the matching between a package and a resource kind is done here
https://github.com/updatecli/updatecli/blob/main/pkg/core/pi... Ideally I would like it to be done at runtime similar to Terraform. If needed you can still use the "shell" target but then you put a strong dependency on the tool used within your script.
Let say that your script call a python tool, then you need to be sure that both your local and ci environment have the same
python version.
I personally consider it as a fallback when I don't have the time to implement something better. Ideally I would like to be able to use resources which are very specific to environment and therefor not suitable for everybody. |