Fuel openstack-config command list does not show full historical data

Detailed bug description:
As launchpad spec [0] states, openstack-config --list should show historical data, but it show only last active configuration.

But after applying of two configuration `list` shows only one in history.

[root@nailgun ~]# fuel openstack-config --env 1 --node 2 --upload --file /tmp/compute.yaml
Openstack configuration with id 9 has been uploaded from file '/tmp/compute.yaml'
[root@nailgun ~]# vim /tmp/compute.yaml
[root@nailgun ~]# fuel openstack-config --env 1 --node 2 --upload --file /tmp/compute.yaml
Openstack configuration with id 10 has been uploaded from file '/tmp/compute.yaml'
[root@nailgun ~]# fuel openstack-config --env 1 --node 2 --list
id | is_active | config_type | cluster_id | node_id | node_role
---|-----------|-------------|------------|---------|----------
10 | True | node | 1 | 2 | None
[root@nailgun ~]# fuel openstack-config --env 1 --node 2 --list --help
usage: fuel openstack-config [-h] [--env ENV] [--file FILE] [--node NODE]
                             [--role ROLE] [--config-id CONFIG-ID] [--deleted]
                             [--force]
                             (--list | --download | --upload | --delete | --execute)

optional arguments:
  -h, --help show this help message and exit
  --env ENV, --env-id ENV
                        environment id
  --file FILE Openstack configuration file
  --node NODE, --node-id NODE
                        Node ID
  --role ROLE, --role ROLE
                        Node role
  --config-id CONFIG-ID
                        Openstack config ID
  --deleted Get deleted configurations
  --force, -f Force configuration update
  --list, -l List openstack configurations
  --download, -d Download current openstack configuration
  --upload, -u Upload new openstack configuration
  --delete Delete openstack configuration
  --execute Apply openstack configuration

Examples:

 Download an existing configuration to file:
        fuel openstack-config --download --config-id 1 --file config.yaml

 Upload new configuration from file:
        fuel openstack-config --upload --env 1 --file config.yaml
        fuel openstack-config --upload --env 1 --node 1 --file config.yaml
        fuel openstack-config --upload --env 1
            --role controller --file config.yaml

 List all available configurations:
        fuel openstack-config --list --env 1
        fuel openstack-config --list --env 1 --node 1
        fuel openstack-config --list --env 1 --deleted

 Delete an existing configuration:
        fuel openstack-config --delete --config 1

 Deploy configuration:
        fuel openstack-config --execute --env 1
        fuel openstack-config --execute --env 1 --node 1
        fuel openstack-config --execute --env 1 --role controller
        fuel openstack-config --execute --env 1 --force

[root@nailgun ~]#

Expected results:
As spec states, user should see historical data on *any* configuration.
For now it is possible to see only previous without any date/time related information.

Actual result:
Only last applied configuration is shown.

Workaround:
User should use database to get historical information.