Note de release pour Mitaka¶
0.8.6¶
Corrections de bugs¶
Fixed a bug when a package containing multi-class yamls could not be added to glare-based catalog.
0.8.5¶
Problèmes de sécurités¶
cve-2016-4972 has been addressed. In ceveral places Murano used loaders inherited directly from yaml.Loader when parsing MuranoPL and UI files from packages. This is unsafe, because this loader is capable of creating custom python objects from specifically constructed yaml files. With this change all yaml loading operations are done using safe loaders instead.
Corrections de bugs¶
cli now makes use of type of the endpoint (defined either as a –os-endpoint-type command line parameter or OS_ENDPOINT_TYPE environment variable). This type defines which interface will be used when connecting to murano, glance and glare APIs.
It is now possible to import packages with “!yaql” tag, when glare is used as backend. Before this fix, importing such package caused a parsing error.
0.8.4¶
Nouvelles fonctionnalités¶
Since glare has been moved to a separate service muranoclient CLI now distinguishes between –glance-url and –glare-url. If –glare-url is not supplied muranoclient requests an endpoint of type “artifact” from keystone.
Corrections de bugs¶
Added fallback from token to username/password if both are provided and token expires or is invalid.
0.8.2¶
Nouvelles fonctionnalités¶
Added python-muranoclient support in openstack-client by setting entry points and implementing interface functions.
Corrections de bugs¶
Fixes use murano package-import with version parameter, It always shows version of client. Rename the parameter “version” to “package-version”
Changed murano-client CLI outputs to show only items affected by current operation instead of full item list.
0.8.1¶
Corrections de bugs¶
fixes no attribute error caused by the new raw_request return, by let the SessionClient raw_request only return response without data.
command “package_update” was broken since murano start support of keystone v3. The error occurred because murano tried to pass custom content type parameter in the request kwargs, not headers.
