Intrinsic functions cannot be called in any order

Bug #1256742 reported by Steve Baker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
Steve Baker

Bug Description

Due to the way function resolution is implemented, the following will work:

Fn::Split: [',', {Fn::Join: [',', [one, two, three]]}]

but the following will not:
Fn::Join: [',', {Fn::Split: [',', 'one,two,three']}]

It should be possible to call any valid combination of intrinsic functions

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/59309

Changed in heat:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/59309
Committed: http://github.com/openstack/heat/commit/8efa2649bce040de1f10ecfe4ba01899039a7837
Submitter: Jenkins
Branch: master

commit 8efa2649bce040de1f10ecfe4ba01899039a7837
Author: Steve Baker <email address hidden>
Date: Mon Dec 2 14:47:23 2013 +1300

    Allow intrinsic functions to be called in any order

    An optional transform function can be passed into the resolve
    functions, which allows transforms to occur on the child snippets.

    Change-Id: I5d9e061c6a55f3939c5e03c780eaad72a001fccc
    Closes-Bug: #1256742

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: icehouse-2 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.