[dashboard] [glare] Specifying abstract base class in the dynamic ui does not yield all of it's descendants in drop-down

[Kirill Zaitsev]

Whenever user specifies a class-dependency in the UI definitions of a package — only that class itself is presented as an option in the dynamic-ui. However engine and api allow to use any package, that has classes, that inherit from the specified class.

Expected result: specifying a class in the UI definitions fetches all the classes, that implement/inherit given class

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/321255
Committed: https://git.openstack.org/cgit/openstack/murano-dashboard/commit/?id=2857c8f4a3eeb6c2db1d2572422ca4c0673ce1ba
Submitter: Jenkins
Branch: master

commit 2857c8f4a3eeb6c2db1d2572422ca4c0673ce1ba
Author: Kirill Zaitsev <email address hidden>
Date: Thu May 26 00:49:07 2016 +0300

    Fetch class descendants in the dynamic_ui from glare

    Before this change whenever a murano-class dependency was specified in
    the ui definition of a package, only packages that contained those
    specific fqns were fetched from API, even though the information about
    inheritance is available in the glare back-end.

    With this change dashboard also fetches all the packages, that have
    classes, that inherit from the specified package. This change also
    alters the way absence of a package is handled. It's now specified as an
    empty field with explanation, rather then a django message. This allows
    having only partial dependencies and skipping optional dependencies
    altogether

    Change-Id: I6632f72ca260c26a116b3aa4608d9592d0f1cbce
    Closes-Bug: #1585812

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/murano-dashboard 3.0.0.0b2 development milestone.