Api-roll 33: 2016-03-14

generated/googleapis_beta/lib/deploymentmanager/v2beta2.dart

 // This is a generated file (see the discoveryapis_generator project).
 
 library googleapis_beta.deploymentmanager.v2beta2;
 
 import 'dart:core' as core;
 import 'dart:async' as async;
 import 'dart:convert' as convert;
 
 import 'package:_discoveryapis_commons/_discoveryapis_commons.dart' as commons;
 import 'package:crypto/crypto.dart' as crypto;
@@ skipping 202 matching lines @@
    * field_name comparison_string literal_string.
    *
    * The field_name is the name of the field you want to compare. Only atomic
    * field types are supported (string, number, boolean). The comparison_string
    * must be either eq (equals) or ne (not equals). The literal_string is the
    * string value to filter to. The literal value must be valid for the type of
    * field you are filtering by (string, number, boolean). For string fields,
    * the literal value is interpreted as a regular expression using RE2 syntax.
    * The literal value must match the entire field.
    *
-   * For example, to filter for instances whose name is not equal to
+   * For example, to filter for instances that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
    * Compute Engine Beta API Only: If you use filtering in the Beta API, you can
    * also filter on nested fields. For example, you could filter on instances
    * that have set the scheduling.automaticRestart field to true. In particular,
    * use filtering on nested fields to take advantage of instance labels to
    * organize and filter results based on label values.
    *
    * The Beta API also supports filtering on multiple expressions by providing
    * each separate expression within parentheses. For example,
    * (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple
-   * expressions are treated as AND expressions meaning that resources must
+   * expressions are treated as AND expressions, meaning that resources must
    * match all expressions to pass the filters.
    *
    * [maxResults] - The maximum number of results per page that should be
    * returned. If the number of available results is larger than maxResults,
    * Compute Engine returns a nextPageToken that can be used to get the next
    * page of results in subsequent list requests.
    * Value must be between "0" and "500".
    *
    * [pageToken] - Specifies a page token to use. Set pageToken to the
    * nextPageToken returned by a previous list request to get the next page of
@@ skipping 273 matching lines @@
    * field_name comparison_string literal_string.
    *
    * The field_name is the name of the field you want to compare. Only atomic
    * field types are supported (string, number, boolean). The comparison_string
    * must be either eq (equals) or ne (not equals). The literal_string is the
    * string value to filter to. The literal value must be valid for the type of
    * field you are filtering by (string, number, boolean). For string fields,
    * the literal value is interpreted as a regular expression using RE2 syntax.
    * The literal value must match the entire field.
    *
-   * For example, to filter for instances whose name is not equal to
+   * For example, to filter for instances that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
    * Compute Engine Beta API Only: If you use filtering in the Beta API, you can
    * also filter on nested fields. For example, you could filter on instances
    * that have set the scheduling.automaticRestart field to true. In particular,
    * use filtering on nested fields to take advantage of instance labels to
    * organize and filter results based on label values.
    *
    * The Beta API also supports filtering on multiple expressions by providing
    * each separate expression within parentheses. For example,
    * (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple
-   * expressions are treated as AND expressions meaning that resources must
+   * expressions are treated as AND expressions, meaning that resources must
    * match all expressions to pass the filters.
    *
    * [maxResults] - The maximum number of results per page that should be
    * returned. If the number of available results is larger than maxResults,
    * Compute Engine returns a nextPageToken that can be used to get the next
    * page of results in subsequent list requests.
    * Value must be between "0" and "500".
    *
    * [pageToken] - Specifies a page token to use. Set pageToken to the
    * nextPageToken returned by a previous list request to get the next page of
@@ skipping 112 matching lines @@
    * field_name comparison_string literal_string.
    *
    * The field_name is the name of the field you want to compare. Only atomic
    * field types are supported (string, number, boolean). The comparison_string
    * must be either eq (equals) or ne (not equals). The literal_string is the
    * string value to filter to. The literal value must be valid for the type of
    * field you are filtering by (string, number, boolean). For string fields,
    * the literal value is interpreted as a regular expression using RE2 syntax.
    * The literal value must match the entire field.
    *
-   * For example, to filter for instances whose name is not equal to
+   * For example, to filter for instances that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
    * Compute Engine Beta API Only: If you use filtering in the Beta API, you can
    * also filter on nested fields. For example, you could filter on instances
    * that have set the scheduling.automaticRestart field to true. In particular,
    * use filtering on nested fields to take advantage of instance labels to
    * organize and filter results based on label values.
    *
    * The Beta API also supports filtering on multiple expressions by providing
    * each separate expression within parentheses. For example,
    * (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple
-   * expressions are treated as AND expressions meaning that resources must
+   * expressions are treated as AND expressions, meaning that resources must
    * match all expressions to pass the filters.
    *
    * [maxResults] - The maximum number of results per page that should be
    * returned. If the number of available results is larger than maxResults,
    * Compute Engine returns a nextPageToken that can be used to get the next
    * page of results in subsequent list requests.
    * Value must be between "0" and "500".
    *
    * [pageToken] - Specifies a page token to use. Set pageToken to the
    * nextPageToken returned by a previous list request to get the next page of
@@ skipping 118 matching lines @@
    * field_name comparison_string literal_string.
    *
    * The field_name is the name of the field you want to compare. Only atomic
    * field types are supported (string, number, boolean). The comparison_string
    * must be either eq (equals) or ne (not equals). The literal_string is the
    * string value to filter to. The literal value must be valid for the type of
    * field you are filtering by (string, number, boolean). For string fields,
    * the literal value is interpreted as a regular expression using RE2 syntax.
    * The literal value must match the entire field.
    *
-   * For example, to filter for instances whose name is not equal to
+   * For example, to filter for instances that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
    * Compute Engine Beta API Only: If you use filtering in the Beta API, you can
    * also filter on nested fields. For example, you could filter on instances
    * that have set the scheduling.automaticRestart field to true. In particular,
    * use filtering on nested fields to take advantage of instance labels to
    * organize and filter results based on label values.
    *
    * The Beta API also supports filtering on multiple expressions by providing
    * each separate expression within parentheses. For example,
    * (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple
-   * expressions are treated as AND expressions meaning that resources must
+   * expressions are treated as AND expressions, meaning that resources must
    * match all expressions to pass the filters.
    *
    * [maxResults] - The maximum number of results per page that should be
    * returned. If the number of available results is larger than maxResults,
    * Compute Engine returns a nextPageToken that can be used to get the next
    * page of results in subsequent list requests.
    * Value must be between "0" and "500".
    *
    * [pageToken] - Specifies a page token to use. Set pageToken to the
    * nextPageToken returned by a previous list request to get the next page of
@@ skipping 66 matching lines @@
    * field_name comparison_string literal_string.
    *
    * The field_name is the name of the field you want to compare. Only atomic
    * field types are supported (string, number, boolean). The comparison_string
    * must be either eq (equals) or ne (not equals). The literal_string is the
    * string value to filter to. The literal value must be valid for the type of
    * field you are filtering by (string, number, boolean). For string fields,
    * the literal value is interpreted as a regular expression using RE2 syntax.
    * The literal value must match the entire field.
    *
-   * For example, to filter for instances whose name is not equal to
+   * For example, to filter for instances that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
    * Compute Engine Beta API Only: If you use filtering in the Beta API, you can
    * also filter on nested fields. For example, you could filter on instances
    * that have set the scheduling.automaticRestart field to true. In particular,
    * use filtering on nested fields to take advantage of instance labels to
    * organize and filter results based on label values.
    *
    * The Beta API also supports filtering on multiple expressions by providing
    * each separate expression within parentheses. For example,
    * (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple
-   * expressions are treated as AND expressions meaning that resources must
+   * expressions are treated as AND expressions, meaning that resources must
    * match all expressions to pass the filters.
    *
    * [maxResults] - The maximum number of results per page that should be
    * returned. If the number of available results is larger than maxResults,
    * Compute Engine returns a nextPageToken that can be used to get the next
    * page of results in subsequent list requests.
    * Value must be between "0" and "500".
    *
    * [pageToken] - Specifies a page token to use. Set pageToken to the
    * nextPageToken returned by a previous list request to get the next page of
@@ skipping 422 matching lines @@
       _json["nextPageToken"] = nextPageToken;
     }
     return _json;
   }
 }
 
 class OperationErrorErrors {
   /** [Output Only] The error type identifier for this error. */
   core.String code;
   /**
-   * [Output Only] Indicates the field in the request which caused the error.
+   * [Output Only] Indicates the field in the request that caused the error.
    * This property is optional.
    */
   core.String location;
   /** [Output Only] An optional, human-readable error message. */
   core.String message;
 
   OperationErrorErrors();
 
   OperationErrorErrors.fromJson(core.Map _json) {
     if (_json.containsKey("code")) {
@@ skipping 49 matching lines @@
     return _json;
   }
 }
 
 class OperationWarningsData {
   /**
    * [Output Only] A key that provides more detail on the warning being
    * returned. For example, for warnings where there are no results in a list
    * request for a particular zone, this key might be scope and the key value
    * might be the zone name. Other examples might be a key indicating a
-   * deprecated resource, and a suggested replacement, or a warning about
-   * invalid network settings (for example, if an instance attempts to perform
-   * IP forwarding but is not enabled for IP forwarding).
+   * deprecated resource and a suggested replacement, or a warning about invalid
+   * network settings (for example, if an instance attempts to perform IP
+   * forwarding but is not enabled for IP forwarding).
    */
   core.String key;
   /** [Output Only] A warning data value corresponding to the key. */
   core.String value;
 
   OperationWarningsData();
 
   OperationWarningsData.fromJson(core.Map _json) {
     if (_json.containsKey("key")) {
       key = _json["key"];
@@ skipping 95 matching lines @@
    * [Output Only] The unique identifier for the resource. This identifier is
    * defined by the server.
    */
   core.String id;
   /**
    * [Output Only] The time that this operation was requested. This value is in
    * RFC3339 text format.
    */
   core.String insertTime;
   /**
-   * [Output Only] Type of the resource. Always compute#operation for Operation
+   * [Output Only] Type of the resource. Always compute#operation for operation
    * resources.
    */
   core.String kind;
   /** [Output Only] Name of the resource. */
   core.String name;
   /**
    * [Output Only] The type of operation, such as insert, update, or delete, and
    * so on.
    */
   core.String operationType;
@@ skipping 563 matching lines @@
     var _json = new core.Map();
     if (nextPageToken != null) {
       _json["nextPageToken"] = nextPageToken;
     }
     if (types != null) {
       _json["types"] = types.map((value) => (value).toJson()).toList();
     }
     return _json;
   }
 }