Allow empty 'config' for software deployment

[huangtianhua]

create a stack with software deployment resource and didn't specific the 'config' property, the stack create failed, the reason is :
http://paste.openstack.org/show/155496/

[OpenStack Infra (hudson-openstack)]

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

[Steve Baker (steve-stevebaker)]

See inline comments in the review, I would prefer the resource to handle missing config or server gracefully rather than making them mandatory

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/144865
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=1e82f2c2c35155e0c441e2c57a7b7c9cca208fce
Submitter: Jenkins
Branch: master

commit 1e82f2c2c35155e0c441e2c57a7b7c9cca208fce
Author: huangtianhua <email address hidden>
Date: Sun Jan 4 16:04:22 2015 +0800

    Allow empty 'config' for software deployment

    Allow empty 'config' for software deployment resource.
    The use case would be for custom agents where the config
    is already baked into the image, so these agents would
    still want to:
      read input_values to feed into the baked-in config
      signal heat that deployment is complete, including output values

    Change-Id: I616640f7fa158576ca65ee7ed4075c38928a81a9
    Closes-Bug: #1407387

[Steve Baker (steve-stevebaker)]

does this mean that there are tripleo templates which have deployment resources which don't specify a config_id?

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/164115
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=a272b3f8d913016a19f09c04c740e43fbd871d11
Submitter: Jenkins
Branch: master

commit a272b3f8d913016a19f09c04c740e43fbd871d11
Author: huangtianhua <email address hidden>
Date: Fri Mar 13 16:14:05 2015 +0800

    Allow empty 'config' for software deployments

    Allow empty 'config' for software deployment resources.
    The use case would be for custom agents where the config
    is already baked into the image, so these agents would
    still want to:
      read input_values to feed into the baked-in config
      signal heat that deployment is complete, including output values

    Change-Id: I87807065bf5821bcff23810d7e58c34eaa991f19
    Closes-Bug: #1407387