Changes between Version 43 and Version 44 of CloudPlugin
- Timestamp:
- Jun 9, 2011, 2:36:11 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CloudPlugin
v43 v44 114 114 {{{ 115 115 [cloud.instance] 116 title = Instances116 title = EC2 Instances 117 117 order = 1 118 label = Instance118 label = EC2 Instance 119 119 description = AWS EC2 instances. 120 120 }}} … … 141 141 }}} 142 142 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: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. 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: 144 144 145 145 * A field can define a search index instead of options … … 147 147 148 148 ===== 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.inifile. For example, a field defined like this: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: 150 150 {{{ 151 151 [cloud.instance] … … 179 179 .. 180 180 crud_view = name, ec2.instance_type, ohai_time, .. 181 crud_new = r oles, created_by, created_at, ..182 crud_edit = r oles, created_by, created_at*, ..181 crud_new = run_list, created_by, created_at, .. 182 crud_edit = run_list, created_by, created_at*, .. 183 183 184 184 grid_columns = name, ec2.instance_type, ohai_time, ..
