Here is the full story:

real YAML that is generated is stored in murano database in packages table.
Murano Dashboard obtains form definitions in YAML from API. But to improve
performance it also caches them locally. And when it does it stores them in
Python pickle format [1] rather then original YAML, but doesn't change the
extension (actually this is a bug). That's why when you take yamls from
dashboard cache they doesn't look like a valid YAML though they contain the
same information and can be decrypted back (that's what I did to find the
error you had). But is is much easier to take real YAML from database though

[1]: https://docs.python.org/2/library/pickle.html

Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis

<sla...@mirantis.com>

On Fri, Nov 27, 2015 at 1:25 AM, Vahid S Hashemian <
vahidhashem...@us.ibm.com> wrote:

> Thanks Stan for the pointer.
>
> I removed the line that referred to the 'name' property and now my
> application is added to the environment without any errors.
> However, what I see in ui.yaml still doesn't look like YAML.
>
> I'm attaching samples again.
>
>
> Even for HOT packages the content is not YAML.
>
> Regards,
> --Vahid
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to