maxiv-kitscontrols / lib-maxiv-dsconfig

Tango configuration management tools

lib-maxiv-dsconfig moved to https://gitlab.com/MaxIV/lib-maxiv-dsconfig

lib-maxiv-dsconfig's Issues

Color output should depend on terminal capability

We should only color the output of the commands when the terminal actually supports it.
Also add a flag to disable colors manually.

Use logging instead of print

cleanup prints, wrap colour conventions to the format of the logging handler.

Move to gitlab

For a better integration in our system

Make diff a bit more smarter and performant

Today it dumps the entire database in order to check the diff.
A way to improve the performance would be to check only from the input json.

Remove useless files

The dsconfig project comes with modules which convert xls, csv, magnet to json. From what I remember the tango name project were able to do that. So to make generic the dsconfig we should remove these files.

Work better with scripts, e.g. ansible

Today in ansible we use dsconfig as a python module in order to detect changes properly. But then we get problems with python2/3.

See if we can make the "json2tango" script more suitable for running directly by ansible and still be able to detect if anything was changed. That way we don't have to care what python version is involved. I think return codes don't really work for this as they should be about errors... there must be some similar cases where people have wrapped programs in ansible modules to make them idempotent?

Dump class properties

It would be convenient to be able to dump the class properties for a given class using dsconfig.dump. Intuitively this should be possible by specifying e.g. clss:SomeDeviceClass --class-properties, but this gives no class properties. Instead, a server filter is required, which is unexpected. Both cases should work.