Fuel cli. Warning Message

[Egor Kotko]

{"build_id": "2015-02-23_12-26-17", "ostf_sha": "1a0b2c6618fac098473c2ed5a9af11d3a886a3bb", "build_number": "139", "release_versions": {"2014.2-6.1": {"VERSION": {"build_id": "2015-02-23_12-26-17", "ostf_sha": "1a0b2c6618fac098473c2ed5a9af11d3a886a3bb", "build_number": "139", "api": "1.0", "nailgun_sha": "0bf9b180d149aaca0d20126f920d9338d77041f3", "production": "docker", "python-fuelclient_sha": "5657dbf06fddb74adb61e9668eb579a1c57d8af8", "astute_sha": "d81ff53c2f467151ecde120d3a4d284e3b5b3dfc", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "b975019fabdb429c1869047df18dd792d2163ecc", "fuellib_sha": "e79ea26134fe22ff32657b79a9ad39905d2c81b1"}}}, "auth_required": true, "api": "1.0", "nailgun_sha": "0bf9b180d149aaca0d20126f920d9338d77041f3", "production": "docker", "python-fuelclient_sha": "5657dbf06fddb74adb61e9668eb579a1c57d8af8", "astute_sha": "d81ff53c2f467151ecde120d3a4d284e3b5b3dfc", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "b975019fabdb429c1869047df18dd792d2163ecc", "fuellib_sha": "e79ea26134fe22ff32657b79a9ad39905d2c81b1"}

Steps to reproduce:
1) Execute any command via cli

Expected result:
Command will be executed without appearing any additional message

Actual result:
Command executed with appearing Warning message:

# fuel node
DEPRECATION WARNING: file /etc/fuel/client/config.yaml is found and will be used as a source for settings. However, it deprecated and will not be used by default in the ongoing version of python-fuelclient.

[Roman Prykhodchenko (romcheg)]

A deprecation warning is something that must reach end users. WIthout that they won't notice that in some time their setup will stop working. For us as a development team it's important to update the documentation and not forget to remove this message when the feature is changed.

[Artem Panchenko (apanchenko-8)]

@Roman,

you are right, but seems that in this case Fuel (CLI) developers are end users of 'python-fuelclient' (I believe that now FuelCLI = fuelclient + /etc/fuel/client/config.yaml ?). So if something we use in Fuel CLI is deprecated in fuelclient, we should make appropriate changes in Fuel CLI. Otherwise for Fuel users it will look like we missed something and delivered deprecated things in new release :)

[Roman Prykhodchenko (romcheg)]

@Artem: Fuel's developers are just one group of python-fuelclient users. There is several other ones. I'm unaware of the term FuelCLI and I actually think that no one else does. There is only a project python-fuelclient (which can also be referenced as Fuel Client) which has a configuration file which was required and used by default, i.e., /etc/fuel/client/config.yaml, but won't be used by default in one of the following releases.

There are no exact plans on when that change is going to happen but the idea behind this deprecation warning is to let users know that this file will not be used by default, so it's better for them to explicitly specify it and forget about the problem.

My proposal is to mute the message if the file still exists but a user explicitly set it.