a5ea8a4c55
The nutty cloudforms api passes the template in via parameters. TemplateUrl is better. try: ./bin/heat create my_stack --template-url=https://raw.github.com/asalkeld/heat/master/templates/WordPress_Single_Instance.template Signed-off-by: Angus Salkeld <asalkeld@redhat.com> |
||
|---|---|---|
| bin | ||
| etc | ||
| heat | ||
| templates | ||
| .gitignore | ||
| HACKING.rst | ||
| LICENSE | ||
| README | ||
| babel.cfg | ||
| pylintrc | ||
| setup.cfg | ||
| setup.py | ||
README
This is the beginings of a AWS Cloudformation API written in the style of an openstack project. Why heat? It makes the clouds raise and keeps them there. try: ./bin/heat-api and in another shell ./bin/heat create my_stack --template-file=./templates/getting_started.template --parameters "param1=foo;param2=bar" References: http://docs.amazonwebservices.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/create-stack.html