When I am using heat stack-create -u http://9.110.51.34/heat/f.yaml f, it works well. When I am using horizon, input http://9.110.51.34/heat/f.yaml as url input, it reports error. I checked the code and found heat CLI read the contents and do transform, and put the template contents in `template`, while horizon just put the url to `template_url` and pass it to heat. Below is code, horizon:
kwargs = {}
if cleaned['template_data']: kwargs['template'] = cleaned['template_data']
else: kwargs['template_url'] = cleaned['template_url']
heat cli:
tpl_files, template = template_utils.get_template_contents(...
...
'template': template,
...
You can see horizon is passing the template_url to heat client, so heat client should know the original url. So it should work.
s.yaml and f.yaml is put on a http server, say: 9.110.51. 34/heat/ f.yaml 9.110.51. 34/heat/ s.yaml
http://
http://
When I am using heat stack-create -u http:// 9.110.51. 34/heat/ f.yaml f, it works well. When I am using horizon, input http:// 9.110.51. 34/heat/ f.yaml as url input, it reports error. I checked the code and found heat CLI read the contents and do transform, and put the template contents in `template`, while horizon just put the url to `template_url` and pass it to heat. Below is code, horizon: 'template_ data']:
kwargs[ 'template' ] = cleaned[ 'template_ data']
kwargs[ 'template_ url'] = cleaned[ 'template_ url'] utils.get_ template_ contents( ...
kwargs = {}
if cleaned[
else:
heat cli:
tpl_files, template = template_
...
'template': template,
...
You can see horizon is passing the template_url to heat client, so heat client should know the original url. So it should work.