JSON agent template fail to execute

[Artem Akulshin]

In case of JSON execution plan the Murano engine try to attach script file with base64-encoded name instead of text that is written in the template and the "file not found" error occurs.

How to reproduce:
1. Create application that creates Windows Instance
2. Add Agent call with a Powershell script that can do nothing (say report "hello world")
3. Upload and execute the application

The error will show that it cannot find a file with strange nme (which is your script name, but base64-encoded)

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/422845
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=c657ffce4d9187ed5f356d61364781f0d55f7ba2
Submitter: Jenkins
Branch: master

commit c657ffce4d9187ed5f356d61364781f0d55f7ba2
Author: Stan Lagun <email address hidden>
Date: Thu Jan 19 11:55:15 2017 -0800

    v1 execution plan template processing was fixed

    In v1 execution plans Scripts section must contain a list
    of base64-encoded files. But instead of a file content,
    the file path was encoded.

    Change-Id: Ibb45de6dd2895a308000d083e0603020502d3b0d
    Closes-Bug: #1657839

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/murano 3.2.0 release.