On 22/04/16 01:06, Jason Pascucci wrote:
Hi,
I wanted to add my yaml as new resources (via
/etc/heat/environment.d/default.yaml, but we use some external files in
the OS::Nova::Server personality section.
I think you're describing this bug:
https://bugs.launchpad.net/heat/+bug/1454401
There's a patch proposed but not yet merged:
https://review.openstack.org/#/c/209439/
It looks like the heat cli handles that when you pass yaml to it, but I
couldn’t get it to work either through horizon, or even heat-cli when it
was a get_file from inside of the new resources.
I can see why file:// might not work, but I sort of
expected that at least http://blah would still work within horizon (if
so, I could just stick it in swift somewhere, but alas, no soup).
What’s the fastest path to a workaround?
Fastest path is probably either backport the patch above, or have a
generation process for templates in your global environment (i.e.
/etc/heat/environment.d) that inlines any external files.
I was thinking of making a new resource plugin that
reads the path, and returns the contents so it could be used as a
get_attr, essentially cribbing the code from the heat command line
processing.
You'd want to be very careful with that to make sure that random users
couldn't end up using that resource type in their templates to read
arbitrary files.
cheers,
Zane.
Is there a better/sane way?
Is there some conceptual thing I’m missing that makes
this moot?
Thanks in advance,
JRPascucci
Juniper Networks
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
