![Zane Bitter](/assets/img/avatar_default.png)
Previously the 'after' template passed to Resource.update() was completely resolved. This led to an odd situation where the contents of a resource's template snippet were either unresolved (but parsed) or resolved depending on whether the resource had been updated or not. Resolve (ha!) this discrepancy by passing a version of the template with the intrinsic functions unresolved. Change-Id: I8c11cdc3c28661db689b416833bde34cea12d98a
HEAT
Heat is a service to orchestrate multiple composite cloud applications using templates, through both an OpenStack-native ReST API and a CloudFormation-compatible Query API.
Why heat? It makes the clouds rise and keeps them there.
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
git clone git@github.com:openstack/heat.git
- Wiki: http://wiki.openstack.org/Heat
- Developer docs: http://docs.openstack.org/developer/heat
Python client
https://github.com/openstack/python-heatclient
References
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/create-stack.html
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html
- http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca
We have integration with
Description
Languages
Python
99.5%
Shell
0.5%