Read datasource table properties API doesn't use datasource table id in URI

[Masahito Muroi]

Read datasource table properties API doesn't accept requests with datasource table id when clients call the API. Current API implementation accepts datasource table "name" in this URI.

Current api accepts following:
/v1/data-sources/nova/tables/flavors

API documentation says that the API accepts following:
/v1/data-sources/3f5a0b45-0d83-4f70-884b-91d280d4f317/tables/flavors

This bug affects both congress and python-congressclient.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/183572

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/183574

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/183572
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=c27cebd69a2e7095c301e8bb3b6bd97c8fd27286
Submitter: Jenkins
Branch: master

commit c27cebd69a2e7095c301e8bb3b6bd97c8fd27286
Author: Masahito Muroi <email address hidden>
Date: Fri May 15 04:49:09 2015 +0000

    Using datasource id in Read datasource table properties API

    Congress server only accepts datasource name in URI of read
    datasource table properties API. This patch changes congress to
    use both id and name in URL of the API. Additionally this adds
    test for the API.

    Change-Id: Ida14d7e916824430a90b527bf654b2b049c441d0
    Closes-Bug: #1453645
    Partial-Bug: #1435616

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-congressclient 1.2.0 release.