Hi YaSTees! I had a deeper look into Ladislav's REST API and I found it very flexible and easy to use - and furthermore very straightforward and easy to enhance. It looks as the most promising approach for using it in openQA for testing YaST.
Now the question raises how we can proceed with it and what we actually need to do to get it integrated in YaST's master branch. The benefit we get when integrate it in mainline YaST is that we are able to test an testing unmodified YaST as it also is shipped to the user. Testing a modified system is not really useful as it may behave different to the unmodified system. Possible downsides of the permanent integration would be -> more dependencies bloat the instsys Additional dependencies are: libjsoncpp19 216.7 KiB libmicrohttpd12 145.1 KiB so overall ~360 KiB - not too much -> Opening ports on a system is always a risk. We potentially open security hole when this is part of every customer's system. Making sure it is only enabled when explicitly adding boot params should make it quite safe. Of course we also need a security review before. Maybe we should even mandatory require a user authentication. Alternative option would be to only listen to a UNIX socket or to localhost. Then it could be used from outside through an ssh connection. So I think these downsides are not bringing big trouble. We could consider if it is possible to make it a kind of plug-in. Can it be e.g. be enabled only when both of the libraries above are available in the system? So what do you think about this? Christopher -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
