Bug 1042178

Summary: [RFE][heat]: Allow Plugins to provide custom Fn:: functions
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-heatAssignee: RHOS Maint <rhos-maint>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: unspecifiedCC: ddomingo, markmc, sbaker, sdake, shardy, yeylon
Target Milestone: gaKeywords: FutureFeature
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/heat/+spec/function-plugins
Whiteboard: upstream_milestone_icehouse-rc1 upstream_status_implemented upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-22 19:08:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 21:17:13 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/function-plugins.

Description:

The idea here is to be able to extend the templating system with your own functions.

This will be based on the same plugin system as used for resources. However functions are a bit trickier: there are two sets of functions we run at different times - ones dealing with static data and ones dealing with runtime data. We may need to provide a way to register each type separately.

We also currently apply functions in a fixed order, which is likely (although not guaranteed) to result in everything in the template being able to be resolved. We'll probably need to fix this so that all functions are guaranteed to resolve no matter their order of nesting.

Specification URL (additional information):

None