Api-roll 39: 2016-07-18

generated/googleapis/lib/deploymentmanager/v2.dart

 // This is a generated file (see the discoveryapis_generator project).
 
 library googleapis.deploymentmanager.v2;
 
 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:http/http.dart' as http;
@@ skipping 267 matching lines @@
    * 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 that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
-   * Compute Engine Beta API Only: When 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. Use filtering on
-   * nested fields to take advantage of labels to organize and search for
+   * You can filter on nested fields. For example, you could filter on instances
+   * that have set the scheduling.automaticRestart field to true. Use filtering
+   * on nested fields to take advantage of labels to organize and search for
    * 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
-   * match all expressions to pass the filters.
+   * To filter on multiple expressions, provide 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 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
    * results.
@@ skipping 340 matching lines @@
    * 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 that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
-   * Compute Engine Beta API Only: When 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. Use filtering on
-   * nested fields to take advantage of labels to organize and search for
+   * You can filter on nested fields. For example, you could filter on instances
+   * that have set the scheduling.automaticRestart field to true. Use filtering
+   * on nested fields to take advantage of labels to organize and search for
    * 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
-   * match all expressions to pass the filters.
+   * To filter on multiple expressions, provide 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 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
    * results.
@@ skipping 114 matching lines @@
    * 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 that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
-   * Compute Engine Beta API Only: When 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. Use filtering on
-   * nested fields to take advantage of labels to organize and search for
+   * You can filter on nested fields. For example, you could filter on instances
+   * that have set the scheduling.automaticRestart field to true. Use filtering
+   * on nested fields to take advantage of labels to organize and search for
    * 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
-   * match all expressions to pass the filters.
+   * To filter on multiple expressions, provide 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 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
    * results.
@@ skipping 120 matching lines @@
    * 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 that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
-   * Compute Engine Beta API Only: When 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. Use filtering on
-   * nested fields to take advantage of labels to organize and search for
+   * You can filter on nested fields. For example, you could filter on instances
+   * that have set the scheduling.automaticRestart field to true. Use filtering
+   * on nested fields to take advantage of labels to organize and search for
    * 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
-   * match all expressions to pass the filters.
+   * To filter on multiple expressions, provide 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 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
    * results.
@@ skipping 68 matching lines @@
    * 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 that do not have a name of
    * example-instance, you would use filter=name ne example-instance.
    *
-   * Compute Engine Beta API Only: When 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. Use filtering on
-   * nested fields to take advantage of labels to organize and search for
+   * You can filter on nested fields. For example, you could filter on instances
+   * that have set the scheduling.automaticRestart field to true. Use filtering
+   * on nested fields to take advantage of labels to organize and search for
    * 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
-   * match all expressions to pass the filters.
+   * To filter on multiple expressions, provide 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 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
    * results.
@@ skipping 1597 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;
   }
 }