I am going to bring this up in the team meeting tomorrow, but I figured
I'd send it out here as well. Rather than retype the issue, please look at:
https://bugs.launchpad.net/heat/+bug/1548856
My question is what the desired behavior of template-validate should be,
at least from a historical standpoint of what we've honored in the past.
Before I propose/implement a fix, I want to make sure I'm not violating
any unwritten expectations on how it should work.
On a related note -- and this is going to sound really stupid that I
don't know this answer -- but are there any docs on actually using Heat?
I was looking for docs that may explain what the expectation of
template-validate was but I couldn't really find any.
The wiki links to a number of developer-centric docs (HOT guide,
developer process, etc.). I found the (what I believe to be current)
REST API docs [1] but the only real description is "Validates a template."
Thanks :D
[1] http://developer.openstack.org/api-ref-orchestration-v1.html
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
