Autogenerated update (2018-03-03)
Update: - bigquery_v2 - content_v2 - dataflow_v1b3 - dataproc_v1 - dataproc_v1beta2 - deploymentmanager_alpha - deploymentmanager_v2 - deploymentmanager_v2beta
This commit is contained in:
1 parent
42c5513d45
commit
4efe498900
25 files changed
+1718
-399
No files matched your search
@@ -264,25 +264,22 @@ module Google
|
||||
# @param [String] project
|
||||
# The project ID for this request.
|
||||
# @param [String] filter
|
||||
# Sets a filter `expression` for filtering listed resources. Your `expression`
|
||||
# must be in the format: 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 that do not have a name of example-
|
||||
# instance, you would use name ne example-instance.
|
||||
# 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.
|
||||
# A filter expression that filters resources listed in the response. The
|
||||
# expression must specify the field name, a comparison operator, and the value
|
||||
# that you want to use for filtering. The value must be a string, a number, or a
|
||||
# boolean. The comparison operator must be either =, !=, >, or <.
|
||||
# For example, if you are filtering Compute Engine instances, you can exclude
|
||||
# instances named example-instance by specifying name != example-instance.
|
||||
# You can also filter nested fields. For example, you could specify scheduling.
|
||||
# automaticRestart = false to include instances only if they are not scheduled
|
||||
# for automatic restarts. You can use filtering on nested fields to filter based
|
||||
# on resource labels.
|
||||
# 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.
|
||||
# parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
|
||||
# Intel Skylake"). By default, each expression is an AND expression. However,
|
||||
# you can include AND and OR expressions explicitly. For example, (cpuPlatform =
|
||||
# "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
||||
# automaticRestart = true).
|
||||
# @param [Fixnum] max_results
|
||||
# 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
|
||||
@@ -626,25 +623,22 @@ module Google
|
||||
# @param [String] deployment
|
||||
# The name of the deployment for this request.
|
||||
# @param [String] filter
|
||||
# Sets a filter `expression` for filtering listed resources. Your `expression`
|
||||
# must be in the format: 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 that do not have a name of example-
|
||||
# instance, you would use name ne example-instance.
|
||||
# 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.
|
||||
# A filter expression that filters resources listed in the response. The
|
||||
# expression must specify the field name, a comparison operator, and the value
|
||||
# that you want to use for filtering. The value must be a string, a number, or a
|
||||
# boolean. The comparison operator must be either =, !=, >, or <.
|
||||
# For example, if you are filtering Compute Engine instances, you can exclude
|
||||
# instances named example-instance by specifying name != example-instance.
|
||||
# You can also filter nested fields. For example, you could specify scheduling.
|
||||
# automaticRestart = false to include instances only if they are not scheduled
|
||||
# for automatic restarts. You can use filtering on nested fields to filter based
|
||||
# on resource labels.
|
||||
# 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.
|
||||
# parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
|
||||
# Intel Skylake"). By default, each expression is an AND expression. However,
|
||||
# you can include AND and OR expressions explicitly. For example, (cpuPlatform =
|
||||
# "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
||||
# automaticRestart = true).
|
||||
# @param [Fixnum] max_results
|
||||
# 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
|
||||
@@ -741,25 +735,22 @@ module Google
|
||||
# @param [String] project
|
||||
# The project ID for this request.
|
||||
# @param [String] filter
|
||||
# Sets a filter `expression` for filtering listed resources. Your `expression`
|
||||
# must be in the format: 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 that do not have a name of example-
|
||||
# instance, you would use name ne example-instance.
|
||||
# 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.
|
||||
# A filter expression that filters resources listed in the response. The
|
||||
# expression must specify the field name, a comparison operator, and the value
|
||||
# that you want to use for filtering. The value must be a string, a number, or a
|
||||
# boolean. The comparison operator must be either =, !=, >, or <.
|
||||
# For example, if you are filtering Compute Engine instances, you can exclude
|
||||
# instances named example-instance by specifying name != example-instance.
|
||||
# You can also filter nested fields. For example, you could specify scheduling.
|
||||
# automaticRestart = false to include instances only if they are not scheduled
|
||||
# for automatic restarts. You can use filtering on nested fields to filter based
|
||||
# on resource labels.
|
||||
# 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.
|
||||
# parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
|
||||
# Intel Skylake"). By default, each expression is an AND expression. However,
|
||||
# you can include AND and OR expressions explicitly. For example, (cpuPlatform =
|
||||
# "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
||||
# automaticRestart = true).
|
||||
# @param [Fixnum] max_results
|
||||
# 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
|
||||
@@ -860,25 +851,22 @@ module Google
|
||||
# @param [String] deployment
|
||||
# The name of the deployment for this request.
|
||||
# @param [String] filter
|
||||
# Sets a filter `expression` for filtering listed resources. Your `expression`
|
||||
# must be in the format: 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 that do not have a name of example-
|
||||
# instance, you would use name ne example-instance.
|
||||
# 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.
|
||||
# A filter expression that filters resources listed in the response. The
|
||||
# expression must specify the field name, a comparison operator, and the value
|
||||
# that you want to use for filtering. The value must be a string, a number, or a
|
||||
# boolean. The comparison operator must be either =, !=, >, or <.
|
||||
# For example, if you are filtering Compute Engine instances, you can exclude
|
||||
# instances named example-instance by specifying name != example-instance.
|
||||
# You can also filter nested fields. For example, you could specify scheduling.
|
||||
# automaticRestart = false to include instances only if they are not scheduled
|
||||
# for automatic restarts. You can use filtering on nested fields to filter based
|
||||
# on resource labels.
|
||||
# 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.
|
||||
# parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
|
||||
# Intel Skylake"). By default, each expression is an AND expression. However,
|
||||
# you can include AND and OR expressions explicitly. For example, (cpuPlatform =
|
||||
# "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
||||
# automaticRestart = true).
|
||||
# @param [Fixnum] max_results
|
||||
# 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
|
||||
@@ -937,25 +925,22 @@ module Google
|
||||
# @param [String] project
|
||||
# The project ID for this request.
|
||||
# @param [String] filter
|
||||
# Sets a filter `expression` for filtering listed resources. Your `expression`
|
||||
# must be in the format: 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 that do not have a name of example-
|
||||
# instance, you would use name ne example-instance.
|
||||
# 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.
|
||||
# A filter expression that filters resources listed in the response. The
|
||||
# expression must specify the field name, a comparison operator, and the value
|
||||
# that you want to use for filtering. The value must be a string, a number, or a
|
||||
# boolean. The comparison operator must be either =, !=, >, or <.
|
||||
# For example, if you are filtering Compute Engine instances, you can exclude
|
||||
# instances named example-instance by specifying name != example-instance.
|
||||
# You can also filter nested fields. For example, you could specify scheduling.
|
||||
# automaticRestart = false to include instances only if they are not scheduled
|
||||
# for automatic restarts. You can use filtering on nested fields to filter based
|
||||
# on resource labels.
|
||||
# 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.
|
||||
# parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
|
||||
# Intel Skylake"). By default, each expression is an AND expression. However,
|
||||
# you can include AND and OR expressions explicitly. For example, (cpuPlatform =
|
||||
# "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
||||
# automaticRestart = true).
|
||||
# @param [Fixnum] max_results
|
||||
# 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
|
||||
|
||||
Reference in new issue
Block a user