Public bug reported: Heat templates can specify the order in which UIs should render parameters in the "ParameterGroups" section. Here is an example template that uses this feature:
heat_template_version: 2013-05-23 parameters: password: type: string hidden: true username: type: string some_number: type: number parameter_groups: - parameters: - some_number - parameters: - username - password This is saying that the parameters should be rendered in the following order: - some_number - username - password Optionally, the first parameter can be rendered separated from the other two (i.e. in different fieldsets), since they are in different groups. Horizon ignores all this and renders the parameters in the random order obtained by iterating on the "parameters" dictionary, which is separate from the parameter groups. When I run the above template, I get the order "username", "password", "some_number", which doesn't even match the order in which the parameters are given. ** Affects: horizon Importance: Undecided Assignee: Miguel Grinberg (miguelgrinberg) Status: New ** Changed in: horizon Assignee: (unassigned) => Miguel Grinberg (miguelgrinberg) ** Description changed: Heat templates can specify the order in which UIs should render - parameter order in the "ParameterGroups" section. Here is an example - template that uses this feature: + parameters in the "ParameterGroups" section. Here is an example template + that uses this feature: heat_template_version: 2013-05-23 parameters: - password: - type: string - hidden: true - username: - type: string - some_number: - type: number + password: + type: string + hidden: true + username: + type: string + some_number: + type: number parameter_groups: - parameters: - - some_number + - some_number - parameters: - - username - - password + - username + - password This is saying that the parameters should be rendered in the following order: - some_number - username - password Optionally, the first parameter can be rendered separated from the other two (i.e. in different fieldsets), since they are in different groups. Horizon ignores all this and renders the parameters in the random order obtained by iterating on the "parameters" dictionary, which is separate from the parameter groups. When I run the above template, I get the order "username", "password", "some_number", which doesn't even match the order in which the parameters are given. -- 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/1364567 Title: The launch stack form does not honor stack parameter order Status in OpenStack Dashboard (Horizon): New Bug description: Heat templates can specify the order in which UIs should render parameters in the "ParameterGroups" section. Here is an example template that uses this feature: heat_template_version: 2013-05-23 parameters: password: type: string hidden: true username: type: string some_number: type: number parameter_groups: - parameters: - some_number - parameters: - username - password This is saying that the parameters should be rendered in the following order: - some_number - username - password Optionally, the first parameter can be rendered separated from the other two (i.e. in different fieldsets), since they are in different groups. Horizon ignores all this and renders the parameters in the random order obtained by iterating on the "parameters" dictionary, which is separate from the parameter groups. When I run the above template, I get the order "username", "password", "some_number", which doesn't even match the order in which the parameters are given. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1364567/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp