Can't use pseudo-integer with Fn::Select

Bug #1518337 reported by Thomas Herve
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
Thomas Herve

Bug Description

If I have a mapping looking like

{"1": "foo", "2": "bar"}

I can't use Fn::Select on it, as the first thing it does is casting the index to an integer, and then complain that the index must be a string, even though I passed it as a string properly.

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/248134

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

Reviewed: https://review.openstack.org/248134
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=0373df6094307db43b6e4f4fda01830cdd5aa93b
Submitter: Jenkins
Branch: master

commit 0373df6094307db43b6e4f4fda01830cdd5aa93b
Author: Thomas Herve <email address hidden>
Date: Fri Nov 20 16:17:03 2015 +0100

    Don't force Fn::Select index to integer

    Fn::Select try to cast its index argument to integer in all the cases,
    but it also needs to use it as a string when you give it a mapping. This
    moves the cast after the mapping case has been handled.

    Change-Id: I84ff404d3a26fb51c2048e43851b1ef5e3031d67
    Closes-Bug: #1518337

Changed in heat:
status: In Progress → Fix Committed
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/heat 6.0.0.0b1

This issue was fixed in the openstack/heat 6.0.0.0b1 development milestone.

Changed in heat:
status: Fix Committed → Fix Released
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.