MF-1340 - Add CLI config TOML file

[WashingtonKK]

Pull request title should be MF-XXX - description or NOISSUE - description where XXX is ID of issue that this PR relate to.
Please review the CONTRIBUTING.md file for detailed contributing guidelines.

What does this do?

Creates a TOML file for CLI

Which issue(s) does this PR fix/relate to?

#1340

List any changes that modify/break current functionality

N/A

Have you included tests for your changes?

No

Did you document any new/modified functionality?

No

Notes

[codecov]

Codecov Report

Merging #1858 (79d61bc) into master (ca52a5a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1858   +/-   ##
=======================================
  Coverage   67.43%   67.43%           
=======================================
  Files         118      118           
  Lines        9491     9491           
=======================================
  Hits         6400     6400           
  Misses       2409     2409           
  Partials      682      682           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[SammyOina]

@WashingtonKK please refer to the correct originating issue

[SammyOina]

There is no support in the CLI for parsing most of the config parameters in this PR https://github.com/mainflux/mainflux/blob/aee0081864f9654f0eeb2c08a36ed5350ce04372/cli/config.go#L15-L20.
I also don't think this PR fully addresses the requirements in #1340

[WashingtonKK]

There is no support in the CLI for parsing most of the config parameters in this PR

https://github.com/mainflux/mainflux/blob/aee0081864f9654f0eeb2c08a36ed5350ce04372/cli/config.go#L15-L20

.
I also don't think this PR fully addresses the requirements in #1340

What do you recommend?

Also, @dborovcanin , what do you think?

[dborovcanin]

There is no need to put "flags" and "flags.root", you can use "urls" for root URLs. The same goes for "flags.channels" and "flags.client" - "channel" and "client" are sufficient. Also, rename client to filter or something similar. Once that's done, you need to add the actual parsing and set the CLI config values from this file, like @SammyOina mentioned here.

[dborovcanin]

There is no support in the CLI for parsing most of the config parameters in this PR
https://github.com/mainflux/mainflux/blob/aee0081864f9654f0eeb2c08a36ed5350ce04372/cli/config.go#L15-L20

.
I also don't think this PR fully addresses the requirements in #1340

What do you recommend?

Also, @dborovcanin , what do you think?

Addressed in PR review.

[SammyOina]

For all cases utilizing the fmt and log package to output text use the mainflux logger package instead

[arvindh123]

@WashingtonKK , Configurations in config.toml are not getting configured in SDK,
I tried with users URL it doesn't works

[WashingtonKK]

@WashingtonKK , Configurations in config.toml are not getting configured in SDK, I tried with users URL it doesn't works

@arvindh123 , I have fixed this

[rodneyosodo]

LGTM

[dborovcanin]

Remove this since it is created automatically anyway when you run the CLI.

[drasko]

LGTM