Changes between Version 43 and Version 44 of CloudPlugin


Ignore:
Timestamp:
Jun 9, 2011, 4:36:11 AM (4 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CloudPlugin

    v43 v44  
    114114{{{
    115115[cloud.instance]
    116 title = Instances
     116title = EC2 Instances
    117117order = 1
    118 label = Instance
     118label = EC2 Instance
    119119description = AWS EC2 instances.
    120120}}}
     
    141141}}}
    142142
    143 Each {{{field.*}}} option must map exactly to its chef [http://wiki.opscode.com/display/chef/Attributes attribute] name.  For example, {{{ec2.placement_availability_zone}}} above maps to the {{{ec2}}} attribute namespace and the {{{placement_availability_zone}}} attribute within that namespace in chef.  It's defined as a {{{select}}} field with a display label and several options separated by a pipe ({{{|}}}) just like Trac custom fields.  There are some important differences to Trac custom fields, however:
     143Each {{{field.*}}} option must map exactly to its chef [http://wiki.opscode.com/display/chef/Attributes attribute] name.  For example, {{{ec2.placement_availability_zone}}} above maps to the {{{ec2}}} attribute namespace and the {{{placement_availability_zone}}} attribute within that namespace in chef.  This field is defined as a {{{select}}} field with a display label and several options separated by a pipe ({{{|}}}) just like Trac custom fields.  There are some important differences to Trac custom fields, however:
    144144
    145145 * A field can define a search index instead of options
     
    147147
    148148===== Search indexes for options =====
    149 You may prefer to define a select (or multiselect) field's options by using a chef search index (e.g., the built-in {{{node}}} or {{{role}}}, or a [http://wiki.opscode.com/display/chef/Data+Bags data bag]) instead of listing them in the trac.ini file.  For example, a field defined like this:
     149You may prefer to define a select (or multiselect) field's options by using a chef search index (e.g., the built-in {{{node}}} or {{{role}}}, or a [http://wiki.opscode.com/display/chef/Data+Bags data bag]) instead of listing them in the {{{trac.ini}}} file.  For example, a field defined like this:
    150150{{{
    151151[cloud.instance]
     
    179179 ..
    180180crud_view = name, ec2.instance_type, ohai_time, ..
    181 crud_new = roles, created_by, created_at, ..
    182 crud_edit = roles, created_by, created_at*, ..
     181crud_new = run_list, created_by, created_at, ..
     182crud_edit = run_list, created_by, created_at*, ..
    183183
    184184grid_columns = name, ec2.instance_type, ohai_time, ..