[code_research]

Thank you very much for your attention - however I asked where I can find exact documentation about these things?

"Mr Brown from Suse wrote in a HN thread..." will not be enough as a reliable source of information. Yes, I could just read the source, however I am expecting such an extraordinary important thing that will change my config files to be documented. I need precise information here.

Also it would be important to know how this conflicts with configuration management systems like chef, ansible, puppet etc. - or is yast able to manage multiple workstations itself, so is is a replacement for these tools?

Thanks!

[rbrownsuse]

There is pretty extensive documentation on http://yast.github.io/documentation.html

It doesn't conflict with other configuration management systems. I've used openSUSE extensively with puppet and saltstack.

Many of SUSE's products use other configuration management systems as part of their toolchain, and SUSE are shipping SUSE Manager 3.0 with SaltStack, so their customers are expected to be able to use YaST alongside such a system

[code_research]

Multiple 404 on that page:

http://www.rubydoc.info/github/yast/yast-yast2/

http://yast-core.readthedocs.org/en/latest/

I am not trying to make you angry, but I think I put the finger right on the place where it hurts very much.

There is no clear documentation about what yast does or what it will not do - basically a blackbox. Maybe it will change apache config. Maybe not. Who knows.

[rbrownsuse]

:) fair point..I'll let the YaST team know (or you could if you happen to be on freenode, they live in the #yast channel)

Users know - YaST doesn't change stuff without telling you, that was the point I was trying to make earlier. Users of YaST no longer have to worry about it silently taking over config files, it either co-exists or doesn't do anything without telling the user with great big pop-up boxes first