yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #30610
[Bug 1438138] [NEW] [Heat] Initial values aren't displaying properly in "Launch Stack" form
Public bug reported:
Using json type default data in a template causes annoying
inconsistencies in the second step of creating a stack. For example for
this template:
heat_template_version: 2013-05-23
parameters:
key:
type: string
default: key
description: This is keypair to access into your stack.
db_password:
type: string
default: secrete
hidden: true
metadata:
type: json
default: {"keyvalue": 5}
on the second step there would be "metadata" field with initial value {u'keyvalue': 5}. That is not valid JSON, and pressing "Launch" button would show: "Expecting property name enclosed in double quotes".
** Affects: horizon
Importance: Medium
Assignee: Tatiana Ovchinnikova (tmazur)
Status: New
** Changed in: horizon
Assignee: (unassigned) => Tatiana Ovchinnikova (tmazur)
** Changed in: horizon
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1438138
Title:
[Heat] Initial values aren't displaying properly in "Launch Stack"
form
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Using json type default data in a template causes annoying
inconsistencies in the second step of creating a stack. For example
for this template:
heat_template_version: 2013-05-23
parameters:
key:
type: string
default: key
description: This is keypair to access into your stack.
db_password:
type: string
default: secrete
hidden: true
metadata:
type: json
default: {"keyvalue": 5}
on the second step there would be "metadata" field with initial value {u'keyvalue': 5}. That is not valid JSON, and pressing "Launch" button would show: "Expecting property name enclosed in double quotes".
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1438138/+subscriptions
Follow ups
References