fuelclient "connect" in 9.1 does not define defaults

[Dmitry Sutyagin]

In Timmy project we try to utilize fuelclient library to get data from Fuel. In 9.1 we try to use method "connect" available in fuelclient/__init__.py. In earlier iterations of 9.1 it worked well without passing non-mandatory arguments. Now, however, ( python-fuelclient-9.0.0-1.mos355.noarch ) method "connect" will not set up a working Client object unless either os_username and other non-mandatory parameters are provided, or relevant environment variables are set - this is because this method does not internally use fuelclient_settings.get_settings().

I believe this is a regression and should be fixed. Fuelclient should provide an interface to instantiate Client class with all the default parameters pre-configured.

[Dmitry Sutyagin (dsutyagin)]

I found that the issue originated in Timmy code:
commit https://github.com/adobdin/timmy/commit/a1b43e1cbd435ee2430ba347b574c578f8310130 adds usage of "connect" function and we pass all parameters, however in https://github.com/adobdin/timmy/commit/b052cede2861803c604f76913cf888e01f23dc6f we started to only provide non-default parameters to the "connect" function.

Still I believe that since connect has most parameters as non-mandatory, it should pre-populate mandatory parameters inside Client __init__ to make it work with default values when no parameters are provided from outside.

[Georgy Kibardin (gkibardin)]

It looks like we are in a Zugzwang sitation here - any move would make situation worse by increasing the library API variety.
I would stop making changes here and switch version agnostic clients, such as Timmy to Fuel REST API.