[Config] Main Config File and Config files for specific cases

[roma-glushko]

Description

Currently, we have a possibility to persist most of the arguments in the config file. This kind of important feature as no one wants to remember/retype long params for CLI commands.

As access log analysis is a on-going task and people come back to this task after some time, there is a different reasons and purpose of the analysis.
Example1. Today some performance degradations happened to the website. There is a need to analyze incoming traffic
Example2. Tomorrow, there is a security accident and malicious activity was detected. Need to analyze access logs from another angle.
Example3. Other days, some customer reports some issues with the payment gateways during morning time. Again there is a need to cover log analysis from a different side.

Example4. Now let's assume that case 1, 2, 3 happens relatively frequently and on a couple of projects.

There is an idea to have a solution to cover such workflow which includes less copy-pasting and let's focus on the problem.

Expected behavior

Tango supports the concept of main config file and case-specific config files.

Main config file is a file where all main project-specific information (like base-url, asset patterns, system-ips etc)

Case-specific config file is a file which can override the main config file of the same project and contains configs which are needed to work on the current case/task.

Benefits

• order access log checking workflow