Call for help on goss server validation
![](https://seccdn.libravatar.org/avatar/b0f1dfca392a09aa6af72f5a113f5d11.jpg?s=120&d=mm&r=g)
Hello everybody, you can find the same text Github Discussions[0]. I've just pushed a first draft of a goss[1] server description to the master-goss-branch[1]. Goss is a YAML based serverspec alternative tool for validating a server’s configuration. Means you are able to check if services are configured correctly, if they are running, if users are there and in the right group, if configs are there and if settings are missing, if pkgs are installed, aso. Wouldn't it be nice to just run one command on a Uyuni server to see if something is wrong? To some extend this could be done with goss. But I need help. I'm pretty sure that I missed a lot of things that need to be added to the goss.yaml file. Would be really awesome if I could get some input and help there. To get started you can either go install goss or head over to systemsmanagement/goss[3] and install it from there. Then change the domain in gossvars.yaml and start the validation via 'goss --vars gossvars.yaml v'. To add additional things to check head over to the manual[4] and take a look at the examples[5]. Should be pretty self explanatory. I would be very happy to see PRs coming to master-goss[2]! Cheers, Jochen [0] https://github.com/uyuni-project/uyuni/discussions/3083 [1] https://goss.rocks [2] https://github.com/uyuni-project/uyuni/tree/master-goss [3] https://build.opensuse.org/package/show/systemsmanagement/goss [4] https://github.com/aelsabbahy/goss/blob/master/docs/manual.md [5] https://github.com/aelsabbahy/goss/blob/master/docs/manual.md#example -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer
participants (1)
-
Jochen Breuer