Many-to-one mapping in resource registry is not supported

[Pavlo Shchelokovskyy]

Though seems a bit artifical, it might be useful for testing purposes for mapping many resources to the OS::Heat::None resource.

We also need this to solve bug 1492942 and unblock the gate for heat-templates
(alternatives are to either map each and every resource type to None resource explicitly, or mangle with Keystone creating fake endpoints).

[OpenStack Infra (hudson-openstack)]

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

[Steve Baker (steve-stevebaker)]

This might be too much like a feature to backport to liberty

[Pavlo Shchelokovskyy (pshchelo)]

in fact it turned out this will not solve the heat-template gate problem (see my comment in bug 1492942), so priority may be lowered

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/227875
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=02a0025338953813b3169e44d56f8ea096a1bca5
Submitter: Jenkins
Branch: master

commit 02a0025338953813b3169e44d56f8ea096a1bca5
Author: Pavlo Shchelokovskyy <email address hidden>
Date: Fri Sep 25 14:05:01 2015 +0000

    Allow many-to-one glob mapping in registry

    This allows mapping several resource type to a single type in the
    resource registry.
    Mostly useful for testing (map many to OS::Heat::None).
    Needed to improve the heat-templates gate.

    Change-Id: I5b56c71b5575b73432b0e24df1dc8f8402c17a0c
    Closes-Bug: #1499748
    Related-Bug: #1492942

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/heat 6.0.0.0b2 development milestone.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/heat 6.0.0.0b2 development milestone.