henrikingo commented on issue #118: URL: https://github.com/apache/otava/issues/118#issuecomment-3697036905
So, let's then focus on the most interesting question of yaml and/or cli api for options and test definitions. Thanks for sharing an example. I actually had not realized you can put entire sql statements in the yaml files. This must have been added when you added pgsql support? I remember the prometheus and of course csv cases as simpler than this, but I could remember wrong of course. But okay, it seems we have created a system where users can essentially analyze an arbitrary dataset, connect to many differrent data sources., and do that differently for each test even.. It is starting to feel like we are building Tableu, not just a small utility to help with CI... But I'm ok with that, should it happen. So, realistically we'll have to support a subset of the more complex configuration as yaml only? IMO it would be good if this can be split into a completely separate file, so that the config that is managed with ConfigArgParse is clearly separate and also "just works" without needing to hack ConfigArgParse. For the inherit functionality I still feel this is re-inventing a standard yaml feature (anchors) but I don't feel channging thatis the most urgent thing in the world. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
