Add dfareporting_v2_5, regenerate APIs
This commit is contained in:
1 parent
b4842fc28b
commit
24ef90b583
48 files changed
+28372
-2741
No files matched your search
@@ -233,16 +233,14 @@ module Google
|
||||
# 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 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.
|
||||
# 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.
|
||||
# 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.
|
||||
# @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
|
||||
@@ -505,16 +503,14 @@ module Google
|
||||
# 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 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.
|
||||
# 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.
|
||||
# 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.
|
||||
# @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
|
||||
@@ -613,16 +609,14 @@ module Google
|
||||
# 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 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.
|
||||
# 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.
|
||||
# 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.
|
||||
# @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
|
||||
@@ -725,16 +719,14 @@ module Google
|
||||
# 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 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.
|
||||
# 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.
|
||||
# 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.
|
||||
# @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
|
||||
@@ -795,16 +787,14 @@ module Google
|
||||
# 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 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.
|
||||
# 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.
|
||||
# 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.
|
||||
# @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