The UI is relying on a call to heat to parse and validate the template file https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/stacks/forms.py#L147
which maps through some additonal UI abstraction and python-heatclient to be the same call as heat template-validate -f template.txt -e env.txt
which returns { "Description": "create a network", "Parameters": { "net_name": { "Default": "defaultnet", "Type": "String", "NoEcho": "false", "Description": "Name of private network to be created", "Label": "net_name" } } }
This seems like a bug in Heat to me. The -e parameter is ignored when validating the template.
Thoughts from the heat team?
The UI is relying on a call to heat to parse and validate the template file /github. com/openstack/ horizon/ blob/master/ openstack_ dashboard/ dashboards/ project/ stacks/ forms.py# L147
https:/
which maps through some additonal UI abstraction and python-heatclient to be the same call as
heat template-validate -f template.txt -e env.txt
which returns Description" : "Name of private network to be created",
{
"Description": "create a network",
"Parameters": {
"net_name": {
"Default": "defaultnet",
"Type": "String",
"NoEcho": "false",
"
"Label": "net_name"
}
}
}
This seems like a bug in Heat to me. The -e parameter is ignored when validating the template.
Thoughts from the heat team?