[jira] [Updated] (BROOKLYN-250) displayName in location brooklyn.config not being used

2016-04-07 Thread John McCabe (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BROOKLYN-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John McCabe updated BROOKLYN-250:
-
Description: 
Observed that the {{displayName}} field populated by the location wizard/yaml 
doesn't appear to be used? For example:
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
item:
  type: localhost
  brooklyn.config:
displayName: locationname
{code}
displays as {{locationid}} rather than {{locationname}} (in dropdown lists and 
the catalog page), whereas the following
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
name: locationname
item:
  type: localhost
{code}
displays the string set in the {{name}} element.

If {{name}} isn't present it falls back to using the {{id}}

  was:
Observed that the {{displayName}} field populated by the location wizard/yaml 
doesn't appear to be used? For example:
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
item:
  type: localhost
  brooklyn.config:
displayName: locationname
{code}
displays as {{locationid}} rather than {{locationname}} (in dropdown lists and 
the catalog page), whereas the following
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
name: locationname
item:
  type: localhost
{code}
If {{name}} isn't present it falls back to using the {{id}}


> displayName in location brooklyn.config not being used
> --
>
> Key: BROOKLYN-250
> URL: https://issues.apache.org/jira/browse/BROOKLYN-250
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: John McCabe
>Priority: Minor
> Attachments: catalog.png, dropdown.png
>
>
> Observed that the {{displayName}} field populated by the location wizard/yaml 
> doesn't appear to be used? For example:
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> item:
>   type: localhost
>   brooklyn.config:
> displayName: locationname
> {code}
> displays as {{locationid}} rather than {{locationname}} (in dropdown lists 
> and the catalog page), whereas the following
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> name: locationname
> item:
>   type: localhost
> {code}
> displays the string set in the {{name}} element.
> If {{name}} isn't present it falls back to using the {{id}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (BROOKLYN-250) displayName in location brooklyn.config not being used

2016-04-07 Thread John McCabe (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BROOKLYN-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John McCabe updated BROOKLYN-250:
-
Attachment: dropdown.png

> displayName in location brooklyn.config not being used
> --
>
> Key: BROOKLYN-250
> URL: https://issues.apache.org/jira/browse/BROOKLYN-250
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: John McCabe
>Priority: Minor
> Attachments: catalog.png, dropdown.png
>
>
> Observed that the {{displayName}} field populated by the location wizard 
> doesn't appear to be used? For example:
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> item:
>   type: localhost
>   brooklyn.config:
> displayName: locationname
> {code}
> displays as {{locationid}} rather than {{locationname}} (in dropdown lists 
> and the catalog page), whereas the following
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> name: locationname
> item:
>   type: localhost
> {code}
> If {{name}} isn't present it falls back to using the {{id}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (BROOKLYN-250) displayName in location brooklyn.config not being used

2016-04-07 Thread John McCabe (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BROOKLYN-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John McCabe updated BROOKLYN-250:
-
Description: 
Observed that the {{displayName}} field populated by the location wizard/yaml 
doesn't appear to be used? For example:
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
item:
  type: localhost
  brooklyn.config:
displayName: locationname
{code}
displays as {{locationid}} rather than {{locationname}} (in dropdown lists and 
the catalog page), whereas the following
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
name: locationname
item:
  type: localhost
{code}
If {{name}} isn't present it falls back to using the {{id}}

  was:
Observed that the {{displayName}} field populated by the location wizard (and 
yaml) doesn't appear to be used? For example:
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
item:
  type: localhost
  brooklyn.config:
displayName: locationname
{code}
displays as {{locationid}} rather than {{locationname}} (in dropdown lists and 
the catalog page), whereas the following
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
name: locationname
item:
  type: localhost
{code}
If {{name}} isn't present it falls back to using the {{id}}


> displayName in location brooklyn.config not being used
> --
>
> Key: BROOKLYN-250
> URL: https://issues.apache.org/jira/browse/BROOKLYN-250
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: John McCabe
>Priority: Minor
> Attachments: catalog.png, dropdown.png
>
>
> Observed that the {{displayName}} field populated by the location wizard/yaml 
> doesn't appear to be used? For example:
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> item:
>   type: localhost
>   brooklyn.config:
> displayName: locationname
> {code}
> displays as {{locationid}} rather than {{locationname}} (in dropdown lists 
> and the catalog page), whereas the following
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> name: locationname
> item:
>   type: localhost
> {code}
> If {{name}} isn't present it falls back to using the {{id}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (BROOKLYN-250) displayName in location brooklyn.config not being used

2016-04-07 Thread John McCabe (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BROOKLYN-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John McCabe updated BROOKLYN-250:
-
Description: 
Observed that the {{displayName}} field populated by the location wizard (and 
yaml) doesn't appear to be used? For example:
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
item:
  type: localhost
  brooklyn.config:
displayName: locationname
{code}
displays as {{locationid}} rather than {{locationname}} (in dropdown lists and 
the catalog page), whereas the following
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
name: locationname
item:
  type: localhost
{code}
If {{name}} isn't present it falls back to using the {{id}}

  was:
Observed that the {{displayName}} field populated by the location wizard 
doesn't appear to be used? For example:
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
item:
  type: localhost
  brooklyn.config:
displayName: locationname
{code}
displays as {{locationid}} rather than {{locationname}} (in dropdown lists and 
the catalog page), whereas the following
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
name: locationname
item:
  type: localhost
{code}
If {{name}} isn't present it falls back to using the {{id}}


> displayName in location brooklyn.config not being used
> --
>
> Key: BROOKLYN-250
> URL: https://issues.apache.org/jira/browse/BROOKLYN-250
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: John McCabe
>Priority: Minor
> Attachments: catalog.png, dropdown.png
>
>
> Observed that the {{displayName}} field populated by the location wizard (and 
> yaml) doesn't appear to be used? For example:
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> item:
>   type: localhost
>   brooklyn.config:
> displayName: locationname
> {code}
> displays as {{locationid}} rather than {{locationname}} (in dropdown lists 
> and the catalog page), whereas the following
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> name: locationname
> item:
>   type: localhost
> {code}
> If {{name}} isn't present it falls back to using the {{id}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (BROOKLYN-250) displayName in location brooklyn.config not being used

2016-04-07 Thread John McCabe (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BROOKLYN-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John McCabe updated BROOKLYN-250:
-
Description: 
Observed that the {{displayName}} field populated by the location wizard 
doesn't appear to be used? For example:
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
item:
  type: localhost
  brooklyn.config:
displayName: locationname
{code}
displays as {{locationid}} rather than {{locationname}} (in dropdown lists and 
the catalog page), whereas the following
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
name: locationname
item:
  type: localhost
{code}
If {{name}} isn't present it falls back to using the {{id}}

  was:
Observed that the displayName field populated by the location wizard doesn't 
appear to be used? For example:
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
item:
  type: localhost
  brooklyn.config:
displayName: locationname
{code}
displays as locationid rather than locationname (in dropdown lists and the 
catalog page), whereas the following
{code}
brooklyn.catalog:
  items:
  - id: locationid
itemType: location
name: locationname
item:
  type: localhost
{code}


> displayName in location brooklyn.config not being used
> --
>
> Key: BROOKLYN-250
> URL: https://issues.apache.org/jira/browse/BROOKLYN-250
> Project: Brooklyn
>  Issue Type: Bug
>Affects Versions: 0.9.0
>Reporter: John McCabe
>Priority: Minor
>
> Observed that the {{displayName}} field populated by the location wizard 
> doesn't appear to be used? For example:
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> item:
>   type: localhost
>   brooklyn.config:
> displayName: locationname
> {code}
> displays as {{locationid}} rather than {{locationname}} (in dropdown lists 
> and the catalog page), whereas the following
> {code}
> brooklyn.catalog:
>   items:
>   - id: locationid
> itemType: location
> name: locationname
> item:
>   type: localhost
> {code}
> If {{name}} isn't present it falls back to using the {{id}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)