2858689767
Since Glare support was introduced the 'catalog/packages' part of Murano API (/v1/catalog/packages) became obsolete and was intended to be used for "legacy" (i.e. non-glare-based) package storage. The murano client was supposed to directly call glare to retrieve the packages. However, the "GetPackageUI" call (GET /v1/catalog/packages/%pkg_id%/ui) is different: not all the packages bundle the UI definitions, some require Murano to generate them based on the contents of the package. This is true for HOT-based packages and others, plugin-based ones. In future this will be true for 100% of the packages when the dynamic ui and object model generation is added. Because of this that API should be callable even if Glare is configured as a package storage backend. It should fetch the artifact from glare, unpack it and use whatever plugin-specific logic required to generate the UI definitions for this particular package. This patch introduces appropriate change while maintaining the backwards compatibility: in the legacy mode (i.e. when murano's DB acts as package storage) the UI is read directly from an appropriate DB table without fetching the whole package. This fixes the issue when the HOT-based packages could not be deplpoyed properly with murano-dashboard, but the murano-client has to be updated as well to properly call the modified API even if Glare is enabled. Change-Id: Id9327e4015e1c0a1553c0b1a0151a94ee4da2928 Partial-bug: #1565805
7 lines
309 B
YAML
7 lines
309 B
YAML
---
|
|
fixes:
|
|
- Fixed a bug when the UI dialog was not displayed in Murano Dashboard for
|
|
applications which don't have UI definitions bundled in the package but
|
|
generate them based on the package contents instead. This usually affected
|
|
HOT-based packages and other non-muranopl-based applications.
|