| Index: discovery/googleapis/compute__v1.json
|
| diff --git a/discovery/googleapis/compute__v1.json b/discovery/googleapis/compute__v1.json
|
| index 69efa5a95009e829789272a91f0f79c437436687..8c338ce41f627f116129d27b9ffc36465ba09200 100644
|
| --- a/discovery/googleapis/compute__v1.json
|
| +++ b/discovery/googleapis/compute__v1.json
|
| @@ -29,7 +29,7 @@
|
| "description": "API for the Google Compute Engine service.",
|
| "discoveryVersion": "v1",
|
| "documentationLink": "https://developers.google.com/compute/docs/reference/latest/",
|
| - "etag": "\"bRFOOrZKfO9LweMbPqu0kcu6De8/c55dTQvv4NWDkglZO3_PlmckRzg\"",
|
| + "etag": "\"bRFOOrZKfO9LweMbPqu0kcu6De8/0HKk2qVFNFj4BfRYktkIsjDiv2o\"",
|
| "icons": {
|
| "x16": "https://www.google.com/images/icons/product/compute_engine-16.png",
|
| "x32": "https://www.google.com/images/icons/product/compute_engine-32.png"
|
| @@ -97,13 +97,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -158,7 +158,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -199,7 +199,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -233,7 +233,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -253,7 +253,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves a list of address resources contained within the specified region.",
|
| + "description": "Retrieves a list of addresses contained within the specified region.",
|
| "httpMethod": "GET",
|
| "id": "compute.addresses.list",
|
| "parameterOrder": [
|
| @@ -262,13 +262,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -288,7 +288,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -318,13 +318,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -355,7 +355,7 @@
|
| ]
|
| },
|
| "delete": {
|
| - "description": "Deletes the specified autoscaler resource.",
|
| + "description": "Deletes the specified autoscaler.",
|
| "httpMethod": "DELETE",
|
| "id": "compute.autoscalers.delete",
|
| "parameterOrder": [
|
| @@ -365,7 +365,7 @@
|
| ],
|
| "parameters": {
|
| "autoscaler": {
|
| - "description": "Name of the persistent autoscaler resource to delete.",
|
| + "description": "Name of the autoscaler to delete.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -379,7 +379,7 @@
|
| "type": "string"
|
| },
|
| "zone": {
|
| - "description": "Name of the zone scoping this request.",
|
| + "description": "Name of the zone for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -396,7 +396,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified autoscaler resource.",
|
| + "description": "Returns the specified autoscaler resource. Get a list of available autoscalers by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.autoscalers.get",
|
| "parameterOrder": [
|
| @@ -406,7 +406,7 @@
|
| ],
|
| "parameters": {
|
| "autoscaler": {
|
| - "description": "Name of the persistent autoscaler resource to return.",
|
| + "description": "Name of the autoscaler to return.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -420,7 +420,7 @@
|
| "type": "string"
|
| },
|
| "zone": {
|
| - "description": "Name of the zone scoping this request.",
|
| + "description": "Name of the zone for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -438,7 +438,7 @@
|
| ]
|
| },
|
| "insert": {
|
| - "description": "Creates an autoscaler resource in the specified project using the data included in the request.",
|
| + "description": "Creates an autoscaler in the specified project using the data included in the request.",
|
| "httpMethod": "POST",
|
| "id": "compute.autoscalers.insert",
|
| "parameterOrder": [
|
| @@ -454,7 +454,7 @@
|
| "type": "string"
|
| },
|
| "zone": {
|
| - "description": "Name of the zone scoping this request.",
|
| + "description": "Name of the zone for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -474,7 +474,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves a list of autoscaler resources contained within the specified zone.",
|
| + "description": "Retrieves a list of autoscalers contained within the specified zone.",
|
| "httpMethod": "GET",
|
| "id": "compute.autoscalers.list",
|
| "parameterOrder": [
|
| @@ -483,13 +483,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -509,7 +509,7 @@
|
| "type": "string"
|
| },
|
| "zone": {
|
| - "description": "Name of the zone scoping this request.",
|
| + "description": "Name of the zone for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -527,7 +527,7 @@
|
| ]
|
| },
|
| "patch": {
|
| - "description": "Updates an autoscaler resource in the specified project using the data included in the request. This method supports patch semantics.",
|
| + "description": "Updates an autoscaler in the specified project using the data included in the request. This method supports patch semantics.",
|
| "httpMethod": "PATCH",
|
| "id": "compute.autoscalers.patch",
|
| "parameterOrder": [
|
| @@ -537,7 +537,7 @@
|
| ],
|
| "parameters": {
|
| "autoscaler": {
|
| - "description": "Name of the autoscaler resource to update.",
|
| + "description": "Name of the autoscaler to update.",
|
| "location": "query",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -551,7 +551,7 @@
|
| "type": "string"
|
| },
|
| "zone": {
|
| - "description": "Name of the zone scoping this request.",
|
| + "description": "Name of the zone for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -571,7 +571,7 @@
|
| ]
|
| },
|
| "update": {
|
| - "description": "Updates an autoscaler resource in the specified project using the data included in the request.",
|
| + "description": "Updates an autoscaler in the specified project using the data included in the request.",
|
| "httpMethod": "PUT",
|
| "id": "compute.autoscalers.update",
|
| "parameterOrder": [
|
| @@ -580,7 +580,7 @@
|
| ],
|
| "parameters": {
|
| "autoscaler": {
|
| - "description": "Name of the autoscaler resource to update.",
|
| + "description": "Name of the autoscaler to update.",
|
| "location": "query",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "type": "string"
|
| @@ -593,7 +593,7 @@
|
| "type": "string"
|
| },
|
| "zone": {
|
| - "description": "Name of the zone scoping this request.",
|
| + "description": "Name of the zone for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -650,7 +650,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified BackendService resource.",
|
| + "description": "Returns the specified BackendService resource. Get a list of available backend services by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.backendServices.get",
|
| "parameterOrder": [
|
| @@ -756,13 +756,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -869,7 +869,7 @@
|
| "diskTypes": {
|
| "methods": {
|
| "aggregatedList": {
|
| - "description": "Retrieves an aggregated list of disk type resources.",
|
| + "description": "Retrieves an aggregated list of disk types.",
|
| "httpMethod": "GET",
|
| "id": "compute.diskTypes.aggregatedList",
|
| "parameterOrder": [
|
| @@ -877,13 +877,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -914,7 +914,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified disk type resource.",
|
| + "description": "Returns the specified disk type. Get a list of available disk types by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.diskTypes.get",
|
| "parameterOrder": [
|
| @@ -924,7 +924,7 @@
|
| ],
|
| "parameters": {
|
| "diskType": {
|
| - "description": "Name of the disk type resource to return.",
|
| + "description": "Name of the disk type to return.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -956,7 +956,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves a list of disk type resources available to the specified project.",
|
| + "description": "Retrieves a list of disk types available to the specified project.",
|
| "httpMethod": "GET",
|
| "id": "compute.diskTypes.list",
|
| "parameterOrder": [
|
| @@ -965,13 +965,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -1021,13 +1021,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -1143,7 +1143,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns a specified persistent disk.",
|
| + "description": "Returns a specified persistent disk. Get a list of available persistent disks by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.disks.get",
|
| "parameterOrder": [
|
| @@ -1185,7 +1185,7 @@
|
| ]
|
| },
|
| "insert": {
|
| - "description": "Creates a persistent disk in the specified project using the data included in the request.",
|
| + "description": "Creates a persistent disk in the specified project using the data in the request. You can create a disk with a sourceImage, a sourceSnapshot, or create an empty 200 GB data disk by omitting all properties. You can also create a disk that is larger than the default size by specifying the sizeGb property.",
|
| "httpMethod": "POST",
|
| "id": "compute.disks.insert",
|
| "parameterOrder": [
|
| @@ -1235,13 +1235,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -1283,7 +1283,7 @@
|
| "firewalls": {
|
| "methods": {
|
| "delete": {
|
| - "description": "Deletes the specified firewall resource.",
|
| + "description": "Deletes the specified firewall.",
|
| "httpMethod": "DELETE",
|
| "id": "compute.firewalls.delete",
|
| "parameterOrder": [
|
| @@ -1292,7 +1292,7 @@
|
| ],
|
| "parameters": {
|
| "firewall": {
|
| - "description": "Name of the firewall resource to delete.",
|
| + "description": "Name of the firewall rule to delete.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -1316,7 +1316,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified firewall resource.",
|
| + "description": "Returns the specified firewall.",
|
| "httpMethod": "GET",
|
| "id": "compute.firewalls.get",
|
| "parameterOrder": [
|
| @@ -1325,7 +1325,7 @@
|
| ],
|
| "parameters": {
|
| "firewall": {
|
| - "description": "Name of the firewall resource to return.",
|
| + "description": "Name of the firewall rule to return.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -1350,7 +1350,7 @@
|
| ]
|
| },
|
| "insert": {
|
| - "description": "Creates a firewall resource in the specified project using the data included in the request.",
|
| + "description": "Creates a firewall rule in the specified project using the data included in the request.",
|
| "httpMethod": "POST",
|
| "id": "compute.firewalls.insert",
|
| "parameterOrder": [
|
| @@ -1378,7 +1378,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves the list of firewall resources available to the specified project.",
|
| + "description": "Retrieves the list of firewall rules available to the specified project.",
|
| "httpMethod": "GET",
|
| "id": "compute.firewalls.list",
|
| "parameterOrder": [
|
| @@ -1386,13 +1386,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -1423,7 +1423,7 @@
|
| ]
|
| },
|
| "patch": {
|
| - "description": "Updates the specified firewall resource with the data included in the request. This method supports patch semantics.",
|
| + "description": "Updates the specified firewall rule with the data included in the request. This method supports patch semantics.",
|
| "httpMethod": "PATCH",
|
| "id": "compute.firewalls.patch",
|
| "parameterOrder": [
|
| @@ -1432,7 +1432,7 @@
|
| ],
|
| "parameters": {
|
| "firewall": {
|
| - "description": "Name of the firewall resource to update.",
|
| + "description": "Name of the firewall rule to update.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -1459,7 +1459,7 @@
|
| ]
|
| },
|
| "update": {
|
| - "description": "Updates the specified firewall resource with the data included in the request.",
|
| + "description": "Updates the specified firewall rule with the data included in the request.",
|
| "httpMethod": "PUT",
|
| "id": "compute.firewalls.update",
|
| "parameterOrder": [
|
| @@ -1468,7 +1468,7 @@
|
| ],
|
| "parameters": {
|
| "firewall": {
|
| - "description": "Name of the firewall resource to update.",
|
| + "description": "Name of the firewall rule to update.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -1507,13 +1507,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -1672,13 +1672,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -1797,7 +1797,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified address resource.",
|
| + "description": "Returns the specified address resource. Get a list of available addresses by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.globalAddresses.get",
|
| "parameterOrder": [
|
| @@ -1859,7 +1859,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves a list of global address resources.",
|
| + "description": "Retrieves a list of global addresses.",
|
| "httpMethod": "GET",
|
| "id": "compute.globalAddresses.list",
|
| "parameterOrder": [
|
| @@ -1867,13 +1867,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -1941,7 +1941,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified ForwardingRule resource.",
|
| + "description": "Returns the specified ForwardingRule resource. Get a list of available forwarding rules by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.globalForwardingRules.get",
|
| "parameterOrder": [
|
| @@ -2011,13 +2011,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -2096,13 +2096,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -2163,7 +2163,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Retrieves the specified Operations resource.",
|
| + "description": "Retrieves the specified Operations resource. Get a list of operations by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.globalOperations.get",
|
| "parameterOrder": [
|
| @@ -2205,13 +2205,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -2279,7 +2279,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified HttpHealthCheck resource.",
|
| + "description": "Returns the specified HttpHealthCheck resource. Get a list of available HTTP health checks by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.httpHealthChecks.get",
|
| "parameterOrder": [
|
| @@ -2349,13 +2349,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -2495,7 +2495,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified HttpsHealthCheck resource.",
|
| + "description": "Returns the specified HttpsHealthCheck resource. Get a list of available HTTPS health checks by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.httpsHealthChecks.get",
|
| "parameterOrder": [
|
| @@ -2565,13 +2565,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -2678,7 +2678,7 @@
|
| "images": {
|
| "methods": {
|
| "delete": {
|
| - "description": "Deletes the specified image resource.",
|
| + "description": "Deletes the specified image.",
|
| "httpMethod": "DELETE",
|
| "id": "compute.images.delete",
|
| "parameterOrder": [
|
| @@ -2747,7 +2747,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified image resource.",
|
| + "description": "Returns the specified image. Get a list of available images by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.images.get",
|
| "parameterOrder": [
|
| @@ -2781,7 +2781,7 @@
|
| ]
|
| },
|
| "insert": {
|
| - "description": "Creates an image resource in the specified project using the data included in the request.",
|
| + "description": "Creates an image in the specified project using the data included in the request.",
|
| "httpMethod": "POST",
|
| "id": "compute.images.insert",
|
| "parameterOrder": [
|
| @@ -2820,13 +2820,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -2911,13 +2911,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -3029,7 +3029,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns all of the details about the specified managed instance group.",
|
| + "description": "Returns all of the details about the specified managed instance group. Get a list of available managed instance groups by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.instanceGroupManagers.get",
|
| "parameterOrder": [
|
| @@ -3113,13 +3113,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -3373,7 +3373,7 @@
|
| "instanceGroups": {
|
| "methods": {
|
| "addInstances": {
|
| - "description": "Adds a list of instances to the specified instance group. Read Adding instances for more information.",
|
| + "description": "Adds a list of instances to the specified instance group. All of the instances in the instance group must be in the same network/subnetwork. Read Adding instances for more information.",
|
| "httpMethod": "POST",
|
| "id": "compute.instanceGroups.addInstances",
|
| "parameterOrder": [
|
| @@ -3423,13 +3423,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -3499,7 +3499,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified instance group resource.",
|
| + "description": "Returns the specified instance group. Get a list of available instance groups by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.instanceGroups.get",
|
| "parameterOrder": [
|
| @@ -3583,13 +3583,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -3636,7 +3636,7 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| @@ -3648,7 +3648,7 @@
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -3776,7 +3776,7 @@
|
| "instanceTemplates": {
|
| "methods": {
|
| "delete": {
|
| - "description": "Deletes the specified instance template.",
|
| + "description": "Deletes the specified instance template. If you delete an instance template that is being referenced from another instance group, the instance group will not be able to create or recreate virtual machine instances. Deleting an instance template is permanent and cannot be undone.",
|
| "httpMethod": "DELETE",
|
| "id": "compute.instanceTemplates.delete",
|
| "parameterOrder": [
|
| @@ -3809,7 +3809,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified instance template resource.",
|
| + "description": "Returns the specified instance template. Get a list of available instance templates by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.instanceTemplates.get",
|
| "parameterOrder": [
|
| @@ -3879,13 +3879,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -3971,7 +3971,7 @@
|
| ]
|
| },
|
| "aggregatedList": {
|
| - "description": "Retrieves aggregated list of instance resources.",
|
| + "description": "Retrieves aggregated list of instances.",
|
| "httpMethod": "GET",
|
| "id": "compute.instances.aggregatedList",
|
| "parameterOrder": [
|
| @@ -3979,13 +3979,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -4026,7 +4026,7 @@
|
| ],
|
| "parameters": {
|
| "instance": {
|
| - "description": "Instance name.",
|
| + "description": "The instance name for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -4205,7 +4205,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified instance resource.",
|
| + "description": "Returns the specified Instance resource. Get a list of available instances by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.instances.get",
|
| "parameterOrder": [
|
| @@ -4334,7 +4334,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves the list of instance resources contained within the specified zone.",
|
| + "description": "Retrieves the list of instances contained within the specified zone.",
|
| "httpMethod": "GET",
|
| "id": "compute.instances.list",
|
| "parameterOrder": [
|
| @@ -4343,13 +4343,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -4746,7 +4746,7 @@
|
| "licenses": {
|
| "methods": {
|
| "get": {
|
| - "description": "Returns the specified license resource.",
|
| + "description": "Returns the specified License resource. Get a list of available licenses by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.licenses.get",
|
| "parameterOrder": [
|
| @@ -4755,7 +4755,7 @@
|
| ],
|
| "parameters": {
|
| "license": {
|
| - "description": "Name of the license resource to return.",
|
| + "description": "Name of the License resource to return.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -4784,7 +4784,7 @@
|
| "machineTypes": {
|
| "methods": {
|
| "aggregatedList": {
|
| - "description": "Retrieves an aggregated list of machine type resources.",
|
| + "description": "Retrieves an aggregated list of machine types.",
|
| "httpMethod": "GET",
|
| "id": "compute.machineTypes.aggregatedList",
|
| "parameterOrder": [
|
| @@ -4792,13 +4792,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -4829,7 +4829,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified machine type resource.",
|
| + "description": "Returns the specified machine type. Get a list of available machine types by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.machineTypes.get",
|
| "parameterOrder": [
|
| @@ -4839,7 +4839,7 @@
|
| ],
|
| "parameters": {
|
| "machineType": {
|
| - "description": "Name of the machine type resource to return.",
|
| + "description": "Name of the machine type to return.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -4871,7 +4871,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves a list of machine type resources available to the specified project.",
|
| + "description": "Retrieves a list of machine types available to the specified project.",
|
| "httpMethod": "GET",
|
| "id": "compute.machineTypes.list",
|
| "parameterOrder": [
|
| @@ -4880,13 +4880,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -4928,7 +4928,7 @@
|
| "networks": {
|
| "methods": {
|
| "delete": {
|
| - "description": "Deletes the specified network resource.",
|
| + "description": "Deletes the specified network.",
|
| "httpMethod": "DELETE",
|
| "id": "compute.networks.delete",
|
| "parameterOrder": [
|
| @@ -4937,7 +4937,7 @@
|
| ],
|
| "parameters": {
|
| "network": {
|
| - "description": "Name of the network resource to delete.",
|
| + "description": "Name of the network to delete.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -4961,7 +4961,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified network resource.",
|
| + "description": "Returns the specified network. Get a list of available networks by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.networks.get",
|
| "parameterOrder": [
|
| @@ -4970,7 +4970,7 @@
|
| ],
|
| "parameters": {
|
| "network": {
|
| - "description": "Name of the network resource to return.",
|
| + "description": "Name of the network to return.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -4995,7 +4995,7 @@
|
| ]
|
| },
|
| "insert": {
|
| - "description": "Creates a network resource in the specified project using the data included in the request.",
|
| + "description": "Creates a network in the specified project using the data included in the request.",
|
| "httpMethod": "POST",
|
| "id": "compute.networks.insert",
|
| "parameterOrder": [
|
| @@ -5023,7 +5023,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves the list of network resources available to the specified project.",
|
| + "description": "Retrieves the list of networks available to the specified project.",
|
| "httpMethod": "GET",
|
| "id": "compute.networks.list",
|
| "parameterOrder": [
|
| @@ -5031,13 +5031,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -5072,7 +5072,7 @@
|
| "projects": {
|
| "methods": {
|
| "get": {
|
| - "description": "Returns the specified project resource.",
|
| + "description": "Returns the specified Project resource.",
|
| "httpMethod": "GET",
|
| "id": "compute.projects.get",
|
| "parameterOrder": [
|
| @@ -5241,7 +5241,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "Name of the region scoping this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -5279,7 +5279,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "Name of the region scoping this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -5306,13 +5306,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -5332,7 +5332,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "Name of the region scoping this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -5354,7 +5354,7 @@
|
| "regions": {
|
| "methods": {
|
| "get": {
|
| - "description": "Returns the specified region resource.",
|
| + "description": "Returns the specified Region resource. Get a list of available regions by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.regions.get",
|
| "parameterOrder": [
|
| @@ -5396,13 +5396,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -5437,7 +5437,7 @@
|
| "routes": {
|
| "methods": {
|
| "delete": {
|
| - "description": "Deletes the specified route resource.",
|
| + "description": "Deletes the specified Route resource.",
|
| "httpMethod": "DELETE",
|
| "id": "compute.routes.delete",
|
| "parameterOrder": [
|
| @@ -5453,7 +5453,7 @@
|
| "type": "string"
|
| },
|
| "route": {
|
| - "description": "Name of the route resource to delete.",
|
| + "description": "Name of the Route resource to delete.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -5470,7 +5470,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified route resource.",
|
| + "description": "Returns the specified Route resource. Get a list of available routes by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.routes.get",
|
| "parameterOrder": [
|
| @@ -5486,7 +5486,7 @@
|
| "type": "string"
|
| },
|
| "route": {
|
| - "description": "Name of the route resource to return.",
|
| + "description": "Name of the Route resource to return.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -5504,7 +5504,7 @@
|
| ]
|
| },
|
| "insert": {
|
| - "description": "Creates a route resource in the specified project using the data included in the request.",
|
| + "description": "Creates a Route resource in the specified project using the data included in the request.",
|
| "httpMethod": "POST",
|
| "id": "compute.routes.insert",
|
| "parameterOrder": [
|
| @@ -5532,7 +5532,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves the list of route resources available to the specified project.",
|
| + "description": "Retrieves the list of Route resources available to the specified project.",
|
| "httpMethod": "GET",
|
| "id": "compute.routes.list",
|
| "parameterOrder": [
|
| @@ -5540,13 +5540,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -5614,7 +5614,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified Snapshot resource.",
|
| + "description": "Returns the specified Snapshot resource. Get a list of available snapshots by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.snapshots.get",
|
| "parameterOrder": [
|
| @@ -5656,13 +5656,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -5730,7 +5730,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified SslCertificate resource.",
|
| + "description": "Returns the specified SslCertificate resource. Get a list of available SSL certificates by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.sslCertificates.get",
|
| "parameterOrder": [
|
| @@ -5800,13 +5800,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -5849,13 +5849,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -5927,7 +5927,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified subnetwork.",
|
| + "description": "Returns the specified subnetwork. Get a list of available subnetworks by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.subnetworks.get",
|
| "parameterOrder": [
|
| @@ -6014,13 +6014,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -6095,7 +6095,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified TargetHttpProxy resource.",
|
| + "description": "Returns the specified TargetHttpProxy resource. Get a list of available target HTTP proxies by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.targetHttpProxies.get",
|
| "parameterOrder": [
|
| @@ -6165,13 +6165,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -6218,7 +6218,7 @@
|
| "type": "string"
|
| },
|
| "targetHttpProxy": {
|
| - "description": "Name of the TargetHttpProxy resource whose URL map is to be set.",
|
| + "description": "Name of the TargetHttpProxy to set a URL map for.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -6275,7 +6275,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified TargetHttpsProxy resource.",
|
| + "description": "Returns the specified TargetHttpsProxy resource. Get a list of available target HTTPS proxies by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.targetHttpsProxies.get",
|
| "parameterOrder": [
|
| @@ -6345,13 +6345,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -6398,7 +6398,7 @@
|
| "type": "string"
|
| },
|
| "targetHttpsProxy": {
|
| - "description": "Name of the TargetHttpsProxy resource whose SSLCertificate is to be set.",
|
| + "description": "Name of the TargetHttpsProxy resource to set an SslCertificates resource for.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -6466,13 +6466,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -6544,7 +6544,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified TargetInstance resource.",
|
| + "description": "Returns the specified TargetInstance resource. Get a list of available target instances by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.targetInstances.get",
|
| "parameterOrder": [
|
| @@ -6631,13 +6631,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -6679,7 +6679,7 @@
|
| "targetPools": {
|
| "methods": {
|
| "addHealthCheck": {
|
| - "description": "Adds health check URL to targetPool.",
|
| + "description": "Adds health check URLs to a target pool.",
|
| "httpMethod": "POST",
|
| "id": "compute.targetPools.addHealthCheck",
|
| "parameterOrder": [
|
| @@ -6689,6 +6689,7 @@
|
| ],
|
| "parameters": {
|
| "project": {
|
| + "description": "Project ID for this request.",
|
| "location": "path",
|
| "pattern": "(?:(?:[-a-z0-9]{1,63}\\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?))",
|
| "required": true,
|
| @@ -6702,7 +6703,7 @@
|
| "type": "string"
|
| },
|
| "targetPool": {
|
| - "description": "Name of the TargetPool resource to which health_check_url is to be added.",
|
| + "description": "Name of the target pool to add a health check to.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -6722,7 +6723,7 @@
|
| ]
|
| },
|
| "addInstance": {
|
| - "description": "Adds instance URL to targetPool.",
|
| + "description": "Adds an instance to a target pool.",
|
| "httpMethod": "POST",
|
| "id": "compute.targetPools.addInstance",
|
| "parameterOrder": [
|
| @@ -6732,6 +6733,7 @@
|
| ],
|
| "parameters": {
|
| "project": {
|
| + "description": "Project ID for this request.",
|
| "location": "path",
|
| "pattern": "(?:(?:[-a-z0-9]{1,63}\\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?))",
|
| "required": true,
|
| @@ -6745,7 +6747,7 @@
|
| "type": "string"
|
| },
|
| "targetPool": {
|
| - "description": "Name of the TargetPool resource to which instance_url is to be added.",
|
| + "description": "Name of the TargetPool resource to add instances to.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -6773,13 +6775,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -6810,7 +6812,7 @@
|
| ]
|
| },
|
| "delete": {
|
| - "description": "Deletes the specified TargetPool resource.",
|
| + "description": "Deletes the specified target pool.",
|
| "httpMethod": "DELETE",
|
| "id": "compute.targetPools.delete",
|
| "parameterOrder": [
|
| @@ -6851,7 +6853,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified TargetPool resource.",
|
| + "description": "Returns the specified target pool. Get a list of available target pools by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.targetPools.get",
|
| "parameterOrder": [
|
| @@ -6893,7 +6895,7 @@
|
| ]
|
| },
|
| "getHealth": {
|
| - "description": "Gets the most recent health check results for each IP for the given instance that is referenced by the given TargetPool.",
|
| + "description": "Gets the most recent health check results for each IP for the instance that is referenced by the given target pool.",
|
| "httpMethod": "POST",
|
| "id": "compute.targetPools.getHealth",
|
| "parameterOrder": [
|
| @@ -6903,6 +6905,7 @@
|
| ],
|
| "parameters": {
|
| "project": {
|
| + "description": "Project ID for this request.",
|
| "location": "path",
|
| "pattern": "(?:(?:[-a-z0-9]{1,63}\\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?))",
|
| "required": true,
|
| @@ -6937,7 +6940,7 @@
|
| ]
|
| },
|
| "insert": {
|
| - "description": "Creates a TargetPool resource in the specified project and region using the data included in the request.",
|
| + "description": "Creates a target pool in the specified project and region using the data included in the request.",
|
| "httpMethod": "POST",
|
| "id": "compute.targetPools.insert",
|
| "parameterOrder": [
|
| @@ -6973,7 +6976,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves a list of TargetPool resources available to the specified project and region.",
|
| + "description": "Retrieves a list of target pools available to the specified project and region.",
|
| "httpMethod": "GET",
|
| "id": "compute.targetPools.list",
|
| "parameterOrder": [
|
| @@ -6982,13 +6985,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -7026,7 +7029,7 @@
|
| ]
|
| },
|
| "removeHealthCheck": {
|
| - "description": "Removes health check URL from targetPool.",
|
| + "description": "Removes health check URL from a target pool.",
|
| "httpMethod": "POST",
|
| "id": "compute.targetPools.removeHealthCheck",
|
| "parameterOrder": [
|
| @@ -7036,20 +7039,21 @@
|
| ],
|
| "parameters": {
|
| "project": {
|
| + "description": "Project ID for this request.",
|
| "location": "path",
|
| "pattern": "(?:(?:[-a-z0-9]{1,63}\\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?))",
|
| "required": true,
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "Name of the region scoping this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| "type": "string"
|
| },
|
| "targetPool": {
|
| - "description": "Name of the TargetPool resource to which health_check_url is to be removed.",
|
| + "description": "Name of the target pool to remove health checks from.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7069,7 +7073,7 @@
|
| ]
|
| },
|
| "removeInstance": {
|
| - "description": "Removes instance URL from targetPool.",
|
| + "description": "Removes instance URL from a target pool.",
|
| "httpMethod": "POST",
|
| "id": "compute.targetPools.removeInstance",
|
| "parameterOrder": [
|
| @@ -7079,6 +7083,7 @@
|
| ],
|
| "parameters": {
|
| "project": {
|
| + "description": "Project ID for this request.",
|
| "location": "path",
|
| "pattern": "(?:(?:[-a-z0-9]{1,63}\\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?))",
|
| "required": true,
|
| @@ -7092,7 +7097,7 @@
|
| "type": "string"
|
| },
|
| "targetPool": {
|
| - "description": "Name of the TargetPool resource to which instance_url is to be removed.",
|
| + "description": "Name of the TargetPool resource to remove instances from.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7112,7 +7117,7 @@
|
| ]
|
| },
|
| "setBackup": {
|
| - "description": "Changes backup pool configurations.",
|
| + "description": "Changes a backup target pool's configurations.",
|
| "httpMethod": "POST",
|
| "id": "compute.targetPools.setBackup",
|
| "parameterOrder": [
|
| @@ -7122,7 +7127,7 @@
|
| ],
|
| "parameters": {
|
| "failoverRatio": {
|
| - "description": "New failoverRatio value for the containing target pool.",
|
| + "description": "New failoverRatio value for the target pool.",
|
| "format": "float",
|
| "location": "query",
|
| "type": "number"
|
| @@ -7142,7 +7147,7 @@
|
| "type": "string"
|
| },
|
| "targetPool": {
|
| - "description": "Name of the TargetPool resource for which the backup is to be set.",
|
| + "description": "Name of the TargetPool resource to set a backup pool for.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7166,7 +7171,7 @@
|
| "targetVpnGateways": {
|
| "methods": {
|
| "aggregatedList": {
|
| - "description": "Retrieves an aggregated list of target VPN gateways .",
|
| + "description": "Retrieves an aggregated list of target VPN gateways.",
|
| "httpMethod": "GET",
|
| "id": "compute.targetVpnGateways.aggregatedList",
|
| "parameterOrder": [
|
| @@ -7174,13 +7179,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -7211,7 +7216,7 @@
|
| ]
|
| },
|
| "delete": {
|
| - "description": "Deletes the specified TargetVpnGateway resource.",
|
| + "description": "Deletes the specified target VPN gateway.",
|
| "httpMethod": "DELETE",
|
| "id": "compute.targetVpnGateways.delete",
|
| "parameterOrder": [
|
| @@ -7228,14 +7233,14 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| "type": "string"
|
| },
|
| "targetVpnGateway": {
|
| - "description": "Name of the TargetVpnGateway resource to delete.",
|
| + "description": "Name of the target VPN gateway to delete.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7252,7 +7257,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified TargetVpnGateway resource.",
|
| + "description": "Returns the specified target VPN gateway. Get a list of available target VPN gateways by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.targetVpnGateways.get",
|
| "parameterOrder": [
|
| @@ -7269,14 +7274,14 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| "type": "string"
|
| },
|
| "targetVpnGateway": {
|
| - "description": "Name of the TargetVpnGateway resource to return.",
|
| + "description": "Name of the target VPN gateway to return.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7294,7 +7299,7 @@
|
| ]
|
| },
|
| "insert": {
|
| - "description": "Creates a TargetVpnGateway resource in the specified project and region using the data included in the request.",
|
| + "description": "Creates a target VPN gateway in the specified project and region using the data included in the request.",
|
| "httpMethod": "POST",
|
| "id": "compute.targetVpnGateways.insert",
|
| "parameterOrder": [
|
| @@ -7310,7 +7315,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7330,7 +7335,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves a list of TargetVpnGateway resources available to the specified project and region.",
|
| + "description": "Retrieves a list of target VPN gateways available to the specified project and region.",
|
| "httpMethod": "GET",
|
| "id": "compute.targetVpnGateways.list",
|
| "parameterOrder": [
|
| @@ -7339,13 +7344,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -7365,7 +7370,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7420,7 +7425,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified UrlMap resource.",
|
| + "description": "Returns the specified UrlMap resource. Get a list of available URL maps by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.urlMaps.get",
|
| "parameterOrder": [
|
| @@ -7490,13 +7495,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -7647,13 +7652,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -7701,7 +7706,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7725,7 +7730,7 @@
|
| ]
|
| },
|
| "get": {
|
| - "description": "Returns the specified VpnTunnel resource.",
|
| + "description": "Returns the specified VpnTunnel resource. Get a list of available VPN tunnels by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.vpnTunnels.get",
|
| "parameterOrder": [
|
| @@ -7742,7 +7747,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7783,7 +7788,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7812,13 +7817,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -7838,7 +7843,7 @@
|
| "type": "string"
|
| },
|
| "region": {
|
| - "description": "The name of the region for this request.",
|
| + "description": "Name of the region for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7884,7 +7889,7 @@
|
| "type": "string"
|
| },
|
| "zone": {
|
| - "description": "Name of the zone scoping this request.",
|
| + "description": "Name of the zone for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7922,7 +7927,7 @@
|
| "type": "string"
|
| },
|
| "zone": {
|
| - "description": "Name of the zone scoping this request.",
|
| + "description": "Name of the zone for this request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7949,13 +7954,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -7975,7 +7980,7 @@
|
| "type": "string"
|
| },
|
| "zone": {
|
| - "description": "Name of the zone scoping this request.",
|
| + "description": "Name of the zone for request.",
|
| "location": "path",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "required": true,
|
| @@ -7997,7 +8002,7 @@
|
| "zones": {
|
| "methods": {
|
| "get": {
|
| - "description": "Returns the specified zone resource.",
|
| + "description": "Returns the specified Zone resource. Get a list of available zones by making a list() request.",
|
| "httpMethod": "GET",
|
| "id": "compute.zones.get",
|
| "parameterOrder": [
|
| @@ -8031,7 +8036,7 @@
|
| ]
|
| },
|
| "list": {
|
| - "description": "Retrieves the list of zone resources available to the specified project.",
|
| + "description": "Retrieves the list of Zone resources available to the specified project.",
|
| "httpMethod": "GET",
|
| "id": "compute.zones.list",
|
| "parameterOrder": [
|
| @@ -8039,13 +8044,13 @@
|
| ],
|
| "parameters": {
|
| "filter": {
|
| - "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| + "description": "Sets a filter expression for filtering listed resources, in the form filter={expression}. Your {expression} must be in the format: field_name comparison_string literal_string.\n\nThe 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.\n\nFor example, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nCompute 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.\n\nThe 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.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| "maxResults": {
|
| "default": "500",
|
| - "description": "The maximum number of results per page that Compute Engine should return. 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.",
|
| + "description": "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.",
|
| "format": "uint32",
|
| "location": "query",
|
| "maximum": "500",
|
| @@ -8078,7 +8083,7 @@
|
| }
|
| }
|
| },
|
| - "revision": "20160120",
|
| + "revision": "20160302",
|
| "rootUrl": "https://www.googleapis.com/",
|
| "schemas": {
|
| "AccessConfig": {
|
| @@ -8144,7 +8149,7 @@
|
| "compute.addresses.insert"
|
| ]
|
| },
|
| - "description": "Name of the resource; provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| + "description": "Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "type": "string"
|
| },
|
| @@ -8210,7 +8215,7 @@
|
| "type": "object"
|
| },
|
| "AddressList": {
|
| - "description": "Contains a list of address resources.",
|
| + "description": "Contains a list of addresses.",
|
| "id": "AddressList",
|
| "properties": {
|
| "id": {
|
| @@ -8218,7 +8223,7 @@
|
| "type": "string"
|
| },
|
| "items": {
|
| - "description": "[Output Only] A list of Address resources.",
|
| + "description": "[Output Only] A list of addresses.",
|
| "items": {
|
| "$ref": "Address"
|
| },
|
| @@ -8256,6 +8261,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -8285,6 +8291,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -8294,7 +8301,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -8342,7 +8349,7 @@
|
| "description": "[Input Only] Specifies the parameters for a new disk that will be created alongside the new instance. Use initialization parameters to create boot disks or local SSDs attached to the new instance.\n\nThis property is mutually exclusive with the source property; you can only define one or the other, but not both."
|
| },
|
| "interface": {
|
| - "description": "Specifies the disk interface to use for attaching this disk, either SCSI or NVME. The default is SCSI. For performance characteristics of SCSI over NVMe, see Local SSD performance.",
|
| + "description": "Specifies the disk interface to use for attaching this disk, which is either SCSI or NVME. The default is SCSI. Persistent disks must always use SCSI and the request will fail if you attempt to attach a persistent disk in any other format than SCSI. Local SSDs can use either NVME or SCSI. For performance characteristics of SCSI over NVMe, see Local SSD performance.",
|
| "enum": [
|
| "NVME",
|
| "SCSI"
|
| @@ -8426,11 +8433,12 @@
|
| "type": "object"
|
| },
|
| "Autoscaler": {
|
| + "description": "Represents an Autoscaler resource. Autoscalers allow you to automatically scale virtual machine instances in managed instance groups according to an autoscaling policy that you define. For more information, read Autoscaling Groups of Instances.",
|
| "id": "Autoscaler",
|
| "properties": {
|
| "autoscalingPolicy": {
|
| "$ref": "AutoscalingPolicy",
|
| - "description": "Autoscaling configuration."
|
| + "description": "The configuration parameters for the autoscaling algorithm. You can define one or more of the policies for an autoscaler: cpuUtilization, customMetricUtilizations, and loadBalancingUtilization.\n\nIf none of these are specified, the default will be to autoscale based on cpuUtilization to 0.8 or 80%."
|
| },
|
| "creationTimestamp": {
|
| "description": "[Output Only] Creation timestamp in RFC3339 text format.",
|
| @@ -8447,7 +8455,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#autoscaler",
|
| - "description": "Type of the resource.",
|
| + "description": "[Output Only] Type of the resource. Always compute#autoscaler for autoscalers.",
|
| "type": "string"
|
| },
|
| "name": {
|
| @@ -8465,7 +8473,7 @@
|
| "type": "string"
|
| },
|
| "target": {
|
| - "description": "URL of Instance Group Manager or Replica Pool which will be controlled by Autoscaler.",
|
| + "description": "URL of the managed instance group that this autoscaler will scale.",
|
| "type": "string"
|
| },
|
| "zone": {
|
| @@ -8485,14 +8493,14 @@
|
| "items": {
|
| "additionalProperties": {
|
| "$ref": "AutoscalersScopedList",
|
| - "description": "Name of the scope containing this set of autoscalers."
|
| + "description": "[Output Only] Name of the scope containing this set of autoscalers."
|
| },
|
| "description": "A map of scoped autoscaler lists.",
|
| "type": "object"
|
| },
|
| "kind": {
|
| "default": "compute#autoscalerAggregatedList",
|
| - "description": "Type of resource.",
|
| + "description": "[Output Only] Type of resource. Always compute#autoscalerAggregatedList for aggregated lists of autoscalers.",
|
| "type": "string"
|
| },
|
| "nextPageToken": {
|
| @@ -8507,7 +8515,7 @@
|
| "type": "object"
|
| },
|
| "AutoscalerList": {
|
| - "description": "Contains a list of persistent autoscaler resources.",
|
| + "description": "Contains a list of Autoscaler resources.",
|
| "id": "AutoscalerList",
|
| "properties": {
|
| "id": {
|
| @@ -8523,7 +8531,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#autoscalerList",
|
| - "description": "Type of resource.",
|
| + "description": "[Output Only] Type of resource. Always compute#autoscalerList for lists of autoscalers.",
|
| "type": "string"
|
| },
|
| "nextPageToken": {
|
| @@ -8541,18 +8549,19 @@
|
| "id": "AutoscalersScopedList",
|
| "properties": {
|
| "autoscalers": {
|
| - "description": "List of autoscalers contained in this scope.",
|
| + "description": "[Output Only] List of autoscalers contained in this scope.",
|
| "items": {
|
| "$ref": "Autoscaler"
|
| },
|
| "type": "array"
|
| },
|
| "warning": {
|
| - "description": "Informational warning which replaces the list of autoscalers when the list is empty.",
|
| + "description": "[Output Only] Informational warning which replaces the list of autoscalers when the list is empty.",
|
| "properties": {
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -8582,6 +8591,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -8591,7 +8601,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -8618,16 +8628,16 @@
|
| "id": "AutoscalingPolicy",
|
| "properties": {
|
| "coolDownPeriodSec": {
|
| - "description": "The number of seconds that the Autoscaler should wait between two succeeding changes to the number of virtual machines. You should define an interval that is at least as long as the initialization time of a virtual machine and the time it may take for replica pool to create the virtual machine. The default is 60 seconds.",
|
| + "description": "The number of seconds that the autoscaler should wait before it starts collecting information from a new instance. This prevents the autoscaler from collecting information when the instance is initializing, during which the collected usage would not be reliable. The default time autoscaler waits is 60 seconds.\n\nVirtual machine initialization times might vary because of numerous factors. We recommend that you test how long an instance may take to initialize. To do this, create an instance and time the startup process.",
|
| "format": "int32",
|
| "type": "integer"
|
| },
|
| "cpuUtilization": {
|
| "$ref": "AutoscalingPolicyCpuUtilization",
|
| - "description": "TODO(jbartosik): Add support for scaling based on muliple utilization metrics (take max recommendation). Exactly one utilization policy should be provided. Configuration parameters of CPU based autoscaling policy."
|
| + "description": "Defines the CPU utilization policy that allows the autoscaler to scale based on the average CPU utilization of a managed instance group."
|
| },
|
| "customMetricUtilizations": {
|
| - "description": "Configuration parameters of autoscaling based on custom metric.",
|
| + "description": "Configuration parameters of autoscaling based on a custom metric.",
|
| "items": {
|
| "$ref": "AutoscalingPolicyCustomMetricUtilization"
|
| },
|
| @@ -8638,12 +8648,12 @@
|
| "description": "Configuration parameters of autoscaling based on load balancer."
|
| },
|
| "maxNumReplicas": {
|
| - "description": "The maximum number of replicas that the Autoscaler can scale up to. This field is required for config to be effective. Maximum number of replicas should be not lower than minimal number of replicas. Absolute limit for this value is defined in Autoscaler backend.",
|
| + "description": "The maximum number of instances that the autoscaler can scale up to. This is required when creating or updating an autoscaler. The maximum number of replicas should not be lower than minimal number of replicas.",
|
| "format": "int32",
|
| "type": "integer"
|
| },
|
| "minNumReplicas": {
|
| - "description": "The minimum number of replicas that the Autoscaler can scale down to. Can't be less than 0. If not provided Autoscaler will choose default value depending on maximal number of replicas.",
|
| + "description": "The minimum number of replicas that the autoscaler can scale down to. This cannot be less than 0. If not provided, autoscaler will choose a default value depending on maximum number of instances allowed.",
|
| "format": "int32",
|
| "type": "integer"
|
| }
|
| @@ -8655,7 +8665,7 @@
|
| "id": "AutoscalingPolicyCpuUtilization",
|
| "properties": {
|
| "utilizationTarget": {
|
| - "description": "The target utilization that the Autoscaler should maintain. It is represented as a fraction of used cores. For example: 6 cores used in 8-core VM are represented here as 0.75. Must be a float value between (0, 1]. If not defined, the default is 0.8.",
|
| + "description": "The target CPU utilization that the autoscaler should maintain. Must be a float value in the range (0, 1]. If not specified, the default is 0.8.\n\nIf the CPU level is below the target utilization, the autoscaler scales down the number of instances until it reaches the minimum number of instances you specified or until the average CPU of your instances reaches the target utilization.\n\nIf the average CPU is above the target utilization, the autoscaler scales up until it reaches the maximum number of instances you specified or until the average utilization reaches the target utilization.",
|
| "format": "double",
|
| "type": "number"
|
| }
|
| @@ -8667,16 +8677,16 @@
|
| "id": "AutoscalingPolicyCustomMetricUtilization",
|
| "properties": {
|
| "metric": {
|
| - "description": "Identifier of the metric. It should be a Cloud Monitoring metric. The metric can not have negative values. The metric should be an utilization metric (increasing number of VMs handling requests x times should reduce average value of the metric roughly x times). For example you could use: compute.googleapis.com/instance/network/received_bytes_count.",
|
| + "description": "The identifier of the Cloud Monitoring metric. The metric cannot have negative values and should be a utilization metric, which means that the number of virtual machines handling requests should increase or decrease proportionally to the metric. The metric must also have a label of compute.googleapis.com/resource_id with the value of the instance's unique ID, although this alone does not guarantee that the metric is valid.\n\nFor example, the following is a valid metric:\ncompute.googleapis.com/instance/network/received_bytes_count\n\n\nThe following is not a valid metric because it does not increase or decrease based on usage:\ncompute.googleapis.com/instance/cpu/reserved_cores",
|
| "type": "string"
|
| },
|
| "utilizationTarget": {
|
| - "description": "Target value of the metric which Autoscaler should maintain. Must be a positive value.",
|
| + "description": "Target value of the metric which autoscaler should maintain. Must be a positive value.",
|
| "format": "double",
|
| "type": "number"
|
| },
|
| "utilizationTargetType": {
|
| - "description": "Defines type in which utilization_target is expressed.",
|
| + "description": "Defines how target utilization value is expressed for a Cloud Monitoring metric. Either GAUGE, DELTA_PER_SECOND, or DELTA_PER_MINUTE. If not specified, the default is GAUGE.",
|
| "enum": [
|
| "DELTA_PER_MINUTE",
|
| "DELTA_PER_SECOND",
|
| @@ -8693,11 +8703,11 @@
|
| "type": "object"
|
| },
|
| "AutoscalingPolicyLoadBalancingUtilization": {
|
| - "description": "Load balancing utilization policy.",
|
| + "description": "Configuration parameters of autoscaling based on load balancing.",
|
| "id": "AutoscalingPolicyLoadBalancingUtilization",
|
| "properties": {
|
| "utilizationTarget": {
|
| - "description": "Fraction of backend capacity utilization (set in HTTP load balancing configuration) that Autoscaler should maintain. Must be a positive float value. If not defined, the default is 0.8. For example if your maxRatePerInstance capacity (in HTTP Load Balancing configuration) is set at 10 and you would like to keep number of instances such that each instance receives 7 QPS on average, set this to 0.7.",
|
| + "description": "Fraction of backend capacity utilization (set in HTTP(s) load balancing configuration) that autoscaler should maintain. Must be a positive float value. If not defined, the default is 0.8.",
|
| "format": "double",
|
| "type": "number"
|
| }
|
| @@ -8709,7 +8719,7 @@
|
| "id": "Backend",
|
| "properties": {
|
| "balancingMode": {
|
| - "description": "Specifies the balancing mode for this backend. The default is UTILIZATION but available values are UTILIZATION and RATE.",
|
| + "description": "Specifies the balancing mode for this backend. For global HTTP(S) load balancing, the default is UTILIZATION. Valid values are UTILIZATION and RATE.",
|
| "enum": [
|
| "RATE",
|
| "UTILIZATION"
|
| @@ -8734,12 +8744,12 @@
|
| "type": "string"
|
| },
|
| "maxRate": {
|
| - "description": "The max requests per second (RPS) of the group. Can be used with either balancing mode, but required if RATE mode. For RATE mode, either maxRate or maxRatePerInstance must be set.",
|
| + "description": "The max requests per second (RPS) of the group. Can be used with either RATE or UTILIZATION balancing modes, but required if RATE mode. For RATE mode, either maxRate or maxRatePerInstance must be set.",
|
| "format": "int32",
|
| "type": "integer"
|
| },
|
| "maxRatePerInstance": {
|
| - "description": "The max requests per second (RPS) that a single backed instance can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerInstance must be set.",
|
| + "description": "The max requests per second (RPS) that a single backend instance can handle.This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerInstance must be set.",
|
| "format": "float",
|
| "type": "number"
|
| },
|
| @@ -8803,10 +8813,11 @@
|
| "type": "integer"
|
| },
|
| "portName": {
|
| - "description": "Name of backend port. The same name should appear in the resource views referenced by this service. Required.",
|
| + "description": "Name of backend port. The same name should appear in the instance groups referenced by this service. Required.",
|
| "type": "string"
|
| },
|
| "protocol": {
|
| + "description": "The protocol this BackendService uses to communicate with backends.\n\nPossible values are HTTP, HTTPS, HTTP2, TCP and SSL.",
|
| "enum": [
|
| "HTTP",
|
| "HTTPS"
|
| @@ -8822,7 +8833,7 @@
|
| "type": "string"
|
| },
|
| "timeoutSec": {
|
| - "description": "How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].",
|
| + "description": "How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds.",
|
| "format": "int32",
|
| "type": "integer"
|
| }
|
| @@ -8945,7 +8956,7 @@
|
| "type": "string"
|
| },
|
| "licenses": {
|
| - "description": "Any applicable publicly visible licenses.",
|
| + "description": "[Output Only] Any applicable publicly visible licenses.",
|
| "items": {
|
| "type": "string"
|
| },
|
| @@ -8957,7 +8968,7 @@
|
| "compute.disks.insert"
|
| ]
|
| },
|
| - "description": "Name of the resource; provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| + "description": "Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "type": "string"
|
| },
|
| @@ -8975,11 +8986,11 @@
|
| "type": "string"
|
| },
|
| "sourceImage": {
|
| - "description": "The source image used to create this disk. If the source image is deleted from the system, this field will not be set, even if an image with the same name has been re-created.\n\nWhen creating a disk, you can provide a private (custom) image using the following input, and Compute Engine will use the corresponding image from your project. For example:\n\nglobal/images/my-private-image \n\nOr you can provide an image from a publicly-available project. For example, to use a Debian image from the debian-cloud project, make sure to include the project in the URL:\n\nprojects/debian-cloud/global/images/debian-7-wheezy-vYYYYMMDD \n\nwhere vYYYYMMDD is the image version. The fully-qualified URL will also work in both cases.",
|
| + "description": "The source image used to create this disk. If the source image is deleted from the system, this field will not be set, even if an image with the same name has been re-created.\n\nWhen creating a disk, you can provide a private (custom) image using the following input, and Compute Engine will use the corresponding image from your project. For example:\n\nglobal/images/my-private-image \n\nOr you can provide an image from a publicly-available project. For example, to use a Debian image from the debian-cloud project, make sure to include the project in the URL:\n\nprojects/debian-cloud/global/images/debian-7-wheezy-vYYYYMMDD \n\nwhere vYYYYMMDD is the image version. The fully-qualified URL will also work in both cases.\n\nYou can also specify the latest image for a private image family by replacing the image name suffix with family/family-name. For example:\n\nglobal/images/family/my-private-family \n\nOr you can specify an image family from a publicly-available project. For example, to use the latest Debian 7 from the debian-cloud project, make sure to include the project in the URL:\n\nprojects/debian-cloud/global/images/family/debian-7",
|
| "type": "string"
|
| },
|
| "sourceImageId": {
|
| - "description": "The ID value of the image used to create this disk. This value identifies the exact image that was used to create this persistent disk. For example, if you created the persistent disk from an image that was later deleted and recreated under the same name, the source image ID would identify the exact version of the image that was used.",
|
| + "description": "[Output Only] The ID value of the image used to create this disk. This value identifies the exact image that was used to create this persistent disk. For example, if you created the persistent disk from an image that was later deleted and recreated under the same name, the source image ID would identify the exact version of the image that was used.",
|
| "type": "string"
|
| },
|
| "sourceSnapshot": {
|
| @@ -9007,11 +9018,11 @@
|
| "type": "string"
|
| },
|
| "type": {
|
| - "description": "URL of the disk type resource describing which disk type to use to create the disk; provided by the client when the disk is created.",
|
| + "description": "URL of the disk type resource describing which disk type to use to create the disk. Provide this when creating the disk.",
|
| "type": "string"
|
| },
|
| "users": {
|
| - "description": "Links to the users of the disk (attached instances) in form: project/zones/zone/instances/instance",
|
| + "description": "[Output Only] Links to the users of the disk (attached instances) in form: project/zones/zone/instances/instance",
|
| "items": {
|
| "type": "string"
|
| },
|
| @@ -9090,7 +9101,7 @@
|
| "id": "DiskMoveRequest",
|
| "properties": {
|
| "destinationZone": {
|
| - "description": "The URL of the destination zone to move the disk to. This can be a full or partial URL. For example, the following are all valid URLs to a zone: \n- https://www.googleapis.com/compute/v1/projects/project/zones/zone \n- projects/project/zones/zone \n- zones/zone",
|
| + "description": "The URL of the destination zone to move the disk. This can be a full or partial URL. For example, the following are all valid URLs to a zone: \n- https://www.googleapis.com/compute/v1/projects/project/zones/zone \n- projects/project/zones/zone \n- zones/zone",
|
| "type": "string"
|
| },
|
| "targetDisk": {
|
| @@ -9101,7 +9112,7 @@
|
| "type": "object"
|
| },
|
| "DiskType": {
|
| - "description": "A disk type resource.",
|
| + "description": "A DiskType resource.",
|
| "id": "DiskType",
|
| "properties": {
|
| "creationTimestamp": {
|
| @@ -9183,7 +9194,7 @@
|
| "type": "object"
|
| },
|
| "DiskTypeList": {
|
| - "description": "Contains a list of disk type resources.",
|
| + "description": "Contains a list of disk types.",
|
| "id": "DiskTypeList",
|
| "properties": {
|
| "id": {
|
| @@ -9229,6 +9240,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -9258,6 +9270,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -9267,7 +9280,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -9305,6 +9318,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -9334,6 +9348,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -9343,7 +9358,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -9366,7 +9381,7 @@
|
| "type": "object"
|
| },
|
| "Firewall": {
|
| - "description": "A Firewall resource.",
|
| + "description": "Represents a Firewall resource.",
|
| "id": "Firewall",
|
| "properties": {
|
| "allowed": {
|
| @@ -9374,7 +9389,7 @@
|
| "items": {
|
| "properties": {
|
| "IPProtocol": {
|
| - "description": "The IP protocol that is allowed for this rule. The protocol type is required when creating a firewall. This value can either be one of the following well known protocol strings (tcp, udp, icmp, esp, ah, sctp), or the IP protocol number.",
|
| + "description": "The IP protocol that is allowed for this rule. The protocol type is required when creating a firewall rule. This value can either be one of the following well known protocol strings (tcp, udp, icmp, esp, ah, sctp), or the IP protocol number.",
|
| "type": "string"
|
| },
|
| "ports": {
|
| @@ -9451,7 +9466,7 @@
|
| "type": "object"
|
| },
|
| "FirewallList": {
|
| - "description": "Contains a list of Firewall resources.",
|
| + "description": "Contains a list of firewalls.",
|
| "id": "FirewallList",
|
| "properties": {
|
| "id": {
|
| @@ -9566,7 +9581,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#forwardingRuleAggregatedList",
|
| - "description": "Type of resource.",
|
| + "description": "[Output Only] Type of resource. Always compute#forwardingRuleAggregatedList for lists of forwarding rules.",
|
| "type": "string"
|
| },
|
| "nextPageToken": {
|
| @@ -9627,6 +9642,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -9656,6 +9672,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -9665,7 +9682,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -9688,6 +9705,7 @@
|
| "type": "object"
|
| },
|
| "HealthCheckReference": {
|
| + "description": "A full or valid partial URL to a health check. For example, the following are valid URLs: \n- https://www.googleapis.com/compute/beta/projects/project-id/global/httpHealthChecks/health-check \n- projects/project-id/global/httpHealthChecks/health-check \n- global/httpHealthChecks/health-check",
|
| "id": "HealthCheckReference",
|
| "properties": {
|
| "healthCheck": {
|
| @@ -9782,7 +9800,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#httpHealthCheck",
|
| - "description": "Type of the resource.",
|
| + "description": "[Output Only] Type of the resource. Always compute#httpHealthCheck for HTTP health checks.",
|
| "type": "string"
|
| },
|
| "name": {
|
| @@ -9796,7 +9814,7 @@
|
| "type": "integer"
|
| },
|
| "requestPath": {
|
| - "description": "The request path of the HTTP health check request. The default value is \"/\".",
|
| + "description": "The request path of the HTTP health check request. The default value is /.",
|
| "type": "string"
|
| },
|
| "selfLink": {
|
| @@ -10069,7 +10087,7 @@
|
| "type": "object"
|
| },
|
| "ImageList": {
|
| - "description": "Contains a list of Image resources.",
|
| + "description": "Contains a list of images.",
|
| "id": "ImageList",
|
| "properties": {
|
| "id": {
|
| @@ -10142,7 +10160,7 @@
|
| "compute.instances.insert"
|
| ]
|
| },
|
| - "description": "Full or partial URL of the machine type resource to use for this instance, in the format: zones/zone/machineTypes/ machine-type. This is provided by the client when the instance is created. For example, the following is a valid partial url to a predefined machine type:\n\nzones/us-central1-f/machineTypes/n1-standard-1 \n\nTo create a custom machine type, provide a URL to a machine type in the following format, where CPUS is 1 or an even number up to 32 (2, 4, 6, ... 24, etc), and MEMORY is the total memory for this instance. Memory must be a multiple of 256 MB and must be supplied in MB (e.g. 5 GB of memory is 5120 MB):\n\nzones/zone/machineTypes/custom-CPUS-MEMORY \n\nFor example: zones/us-central1-f/machineTypes/custom-4-5120 \n\nFor a full list of restrictions, read the Specifications for custom machine types.",
|
| + "description": "Full or partial URL of the machine type resource to use for this instance, in the format: zones/zone/machineTypes/machine-type. This is provided by the client when the instance is created. For example, the following is a valid partial url to a predefined machine type:\n\nzones/us-central1-f/machineTypes/n1-standard-1 \n\nTo create a custom machine type, provide a URL to a machine type in the following format, where CPUS is 1 or an even number up to 32 (2, 4, 6, ... 24, etc), and MEMORY is the total memory for this instance. Memory must be a multiple of 256 MB and must be supplied in MB (e.g. 5 GB of memory is 5120 MB):\n\nzones/zone/machineTypes/custom-CPUS-MEMORY \n\nFor example: zones/us-central1-f/machineTypes/custom-4-5120 \n\nFor a full list of restrictions, read the Specifications for custom machine types.",
|
| "type": "string"
|
| },
|
| "metadata": {
|
| @@ -10205,7 +10223,7 @@
|
| },
|
| "tags": {
|
| "$ref": "Tags",
|
| - "description": "A list of tags to appy to this instance. Tags are used to identify valid sources or targets for network firewalls and are specified by the client during instance creation. The tags can be later modified by the setTags method. Each tag within the list must comply with RFC1035."
|
| + "description": "A list of tags to apply to this instance. Tags are used to identify valid sources or targets for network firewalls and are specified by the client during instance creation. The tags can be later modified by the setTags method. Each tag within the list must comply with RFC1035."
|
| },
|
| "zone": {
|
| "description": "[Output Only] URL of the zone where the instance resides.",
|
| @@ -10224,7 +10242,7 @@
|
| "items": {
|
| "additionalProperties": {
|
| "$ref": "InstancesScopedList",
|
| - "description": "Name of the scope containing this set of instances."
|
| + "description": "[Output Only] Name of the scope containing this set of instances."
|
| },
|
| "description": "[Output Only] A map of scoped instance lists.",
|
| "type": "object"
|
| @@ -10289,7 +10307,7 @@
|
| "type": "array"
|
| },
|
| "network": {
|
| - "description": "[Output Only] The URL of the network to which all instances in the instance group belong.",
|
| + "description": "The URL of the network to which all instances in the instance group belong.",
|
| "type": "string"
|
| },
|
| "selfLink": {
|
| @@ -10302,7 +10320,7 @@
|
| "type": "integer"
|
| },
|
| "subnetwork": {
|
| - "description": "[Output Only] The URL of the subnetwork to which all instances in the instance group belong.",
|
| + "description": "The URL of the subnetwork to which all instances in the instance group belong.",
|
| "type": "string"
|
| },
|
| "zone": {
|
| @@ -10375,7 +10393,6 @@
|
| "type": "object"
|
| },
|
| "InstanceGroupManager": {
|
| - "description": "InstanceGroupManagers\n\nNext available tag: 20",
|
| "id": "InstanceGroupManager",
|
| "properties": {
|
| "baseInstanceName": {
|
| @@ -10644,6 +10661,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -10673,6 +10691,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -10682,7 +10701,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -10822,6 +10841,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -10851,6 +10871,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -10860,7 +10881,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -10901,7 +10922,7 @@
|
| "type": "object"
|
| },
|
| "InstanceList": {
|
| - "description": "Contains a list of instance resources.",
|
| + "description": "Contains a list of instances.",
|
| "id": "InstanceList",
|
| "properties": {
|
| "id": {
|
| @@ -10909,7 +10930,7 @@
|
| "type": "string"
|
| },
|
| "items": {
|
| - "description": "[Output Only] A list of Instance resources.",
|
| + "description": "[Output Only] A list of instances.",
|
| "items": {
|
| "$ref": "Instance"
|
| },
|
| @@ -10935,7 +10956,7 @@
|
| "id": "InstanceMoveRequest",
|
| "properties": {
|
| "destinationZone": {
|
| - "description": "The URL of the destination zone to move the instance to. This can be a full or partial URL. For example, the following are all valid URLs to a zone: \n- https://www.googleapis.com/compute/v1/projects/project/zones/zone \n- projects/project/zones/zone \n- zones/zone",
|
| + "description": "The URL of the destination zone to move the instance. This can be a full or partial URL. For example, the following are all valid URLs to a zone: \n- https://www.googleapis.com/compute/v1/projects/project/zones/zone \n- projects/project/zones/zone \n- zones/zone",
|
| "type": "string"
|
| },
|
| "targetInstance": {
|
| @@ -11143,6 +11164,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -11172,6 +11194,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -11181,7 +11204,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -11356,7 +11379,7 @@
|
| "type": "object"
|
| },
|
| "MachineTypeList": {
|
| - "description": "Contains a list of Machine Type resources.",
|
| + "description": "Contains a list of machine types.",
|
| "id": "MachineTypeList",
|
| "properties": {
|
| "id": {
|
| @@ -11402,6 +11425,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -11431,6 +11455,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -11440,7 +11465,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -11542,7 +11567,7 @@
|
| "type": "string"
|
| },
|
| "location": {
|
| - "description": "[Output Only] Indicates the field in the request which caused the error. This property is optional.",
|
| + "description": "[Output Only] Indicates the field in the request that caused the error. This property is optional.",
|
| "type": "string"
|
| },
|
| "message": {
|
| @@ -11624,7 +11649,7 @@
|
| "type": "object"
|
| },
|
| "Network": {
|
| - "description": "A network resource.",
|
| + "description": "Represents a Network resource. Read Networks and Firewalls for more information.",
|
| "id": "Network",
|
| "properties": {
|
| "IPv4Range": {
|
| @@ -11719,7 +11744,7 @@
|
| "type": "object"
|
| },
|
| "NetworkList": {
|
| - "description": "Contains a list of Network resources.",
|
| + "description": "Contains a list of networks.",
|
| "id": "NetworkList",
|
| "properties": {
|
| "id": {
|
| @@ -11754,7 +11779,7 @@
|
| "id": "Operation",
|
| "properties": {
|
| "clientOperationId": {
|
| - "description": "[Output Only] A unique client ID generated by the server.",
|
| + "description": "[Output Only] Reserved for future use.",
|
| "type": "string"
|
| },
|
| "creationTimestamp": {
|
| @@ -11781,7 +11806,7 @@
|
| "type": "string"
|
| },
|
| "location": {
|
| - "description": "[Output Only] Indicates the field in the request which caused the error. This property is optional.",
|
| + "description": "[Output Only] Indicates the field in the request that caused the error. This property is optional.",
|
| "type": "string"
|
| },
|
| "message": {
|
| @@ -11816,7 +11841,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#operation",
|
| - "description": "[Output Only] Type of the resource. Always compute#operation for Operation resources.",
|
| + "description": "[Output Only] Type of the resource. Always compute#operation for operation resources.",
|
| "type": "string"
|
| },
|
| "name": {
|
| @@ -11824,7 +11849,7 @@
|
| "type": "string"
|
| },
|
| "operationType": {
|
| - "description": "[Output Only] The type of operation, which can be insert, update, or delete.",
|
| + "description": "[Output Only] The type of operation, such as insert, update, or delete, and so on.",
|
| "type": "string"
|
| },
|
| "progress": {
|
| @@ -11833,7 +11858,7 @@
|
| "type": "integer"
|
| },
|
| "region": {
|
| - "description": "[Output Only] URL of the region where the operation resides. Only available when performing regional operations.",
|
| + "description": "[Output Only] The URL of the region where the operation resides. Only available when performing regional operations.",
|
| "type": "string"
|
| },
|
| "selfLink": {
|
| @@ -11868,7 +11893,7 @@
|
| "type": "string"
|
| },
|
| "targetLink": {
|
| - "description": "[Output Only] The URL of the resource that the operation is modifying.",
|
| + "description": "[Output Only] The URL of the resource that the operation modifies.",
|
| "type": "string"
|
| },
|
| "user": {
|
| @@ -11882,6 +11907,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -11911,6 +11937,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -11920,7 +11947,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -11942,7 +11969,7 @@
|
| "type": "array"
|
| },
|
| "zone": {
|
| - "description": "[Output Only] URL of the zone where the operation resides. Only available when performing per-zone operations.",
|
| + "description": "[Output Only] The URL of the zone where the operation resides. Only available when performing per-zone operations.",
|
| "type": "string"
|
| }
|
| },
|
| @@ -11988,7 +12015,7 @@
|
| "type": "string"
|
| },
|
| "items": {
|
| - "description": "[Output Only] The Operation resources.",
|
| + "description": "[Output Only] A list of Operation resources.",
|
| "items": {
|
| "$ref": "Operation"
|
| },
|
| @@ -12026,6 +12053,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -12055,6 +12083,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -12064,7 +12093,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -12131,7 +12160,7 @@
|
| "type": "object"
|
| },
|
| "Project": {
|
| - "description": "A Project resource. Projects can only be created in the Google Developers Console. Unless marked otherwise, values can only be modified in the console.",
|
| + "description": "A Project resource. Projects can only be created in the Google Cloud Platform Console. Unless marked otherwise, values can only be modified in the console.",
|
| "id": "Project",
|
| "properties": {
|
| "commonInstanceMetadata": {
|
| @@ -12371,7 +12400,7 @@
|
| "type": "object"
|
| },
|
| "Route": {
|
| - "description": "The route resource. A Route is a rule that specifies how certain packets should be handled by the virtual network. Routes are associated with instances by tags and the set of Routes for a particular instance is called its routing table. For each packet leaving a instance, the system searches that instance's routing table for a single best matching Route. Routes match packets by destination IP address, preferring smaller or more specific ranges over larger ones. If there is a tie, the system selects the Route with the smallest priority value. If there is still a tie, it uses the layer three and four packet headers to select just one of the remaining matching Routes. The packet is then forwarded as specified by the nextHop field of the winning Route -- either to another instance destination, a instance gateway or a Google Compute Engien-operated gateway. Packets that do not match any Route in the sending instance's routing table are dropped.",
|
| + "description": "Represents a Route resource. A route specifies how certain packets should be handled by the network. Routes are associated with instances by tags and the set of routes for a particular instance is called its routing table.\n\nFor each packet leaving a instance, the system searches that instance's routing table for a single best matching route. Routes match packets by destination IP address, preferring smaller or more specific ranges over larger ones. If there is a tie, the system selects the route with the smallest priority value. If there is still a tie, it uses the layer three and four packet headers to select just one of the remaining matching routes. The packet is then forwarded as specified by the nextHop field of the winning route - either to another instance destination, a instance gateway or a Google Compute Engine-operated gateway.\n\nPackets that do not match any route in the sending instance's routing table are dropped.",
|
| "id": "Route",
|
| "properties": {
|
| "creationTimestamp": {
|
| @@ -12407,7 +12436,7 @@
|
| "compute.routes.insert"
|
| ]
|
| },
|
| - "description": "Name of the resource; provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| + "description": "Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "type": "string"
|
| },
|
| @@ -12473,6 +12502,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -12502,6 +12532,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -12511,7 +12542,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -12536,7 +12567,7 @@
|
| "type": "object"
|
| },
|
| "RouteList": {
|
| - "description": "Contains a list of route resources.",
|
| + "description": "Contains a list of Route resources.",
|
| "id": "RouteList",
|
| "properties": {
|
| "id": {
|
| @@ -12575,7 +12606,7 @@
|
| "type": "boolean"
|
| },
|
| "onHostMaintenance": {
|
| - "description": "Defines the maintenance behavior for this instance. For standard instances, the default behavior is MIGRATE. For preemptible instances, the default and only possible behavior is TERMINATE. For more information, see Setting maintenance behavior.",
|
| + "description": "Defines the maintenance behavior for this instance. For standard instances, the default behavior is MIGRATE. For preemptible instances, the default and only possible behavior is TERMINATE. For more information, see Setting Instance Scheduling Options.",
|
| "enum": [
|
| "MIGRATE",
|
| "TERMINATE"
|
| @@ -12659,7 +12690,7 @@
|
| "type": "string"
|
| },
|
| "licenses": {
|
| - "description": "Public visible licenses.",
|
| + "description": "[Output Only] A list of public visible licenses that apply to this snapshot. This can be because the original image had licenses attached (such as a Windows image).",
|
| "items": {
|
| "type": "string"
|
| },
|
| @@ -12683,7 +12714,7 @@
|
| "type": "string"
|
| },
|
| "status": {
|
| - "description": "[Output Only] The status of the snapshot.",
|
| + "description": "[Output Only] The status of the snapshot. This can be CREATING, DELETING, FAILED, READY, or UPLOADING.",
|
| "enum": [
|
| "CREATING",
|
| "DELETING",
|
| @@ -12706,7 +12737,7 @@
|
| "type": "string"
|
| },
|
| "storageBytesStatus": {
|
| - "description": "[Output Only] An indicator whether storageBytes is in a stable state or it is being adjusted as a result of shared storage reallocation.",
|
| + "description": "[Output Only] An indicator whether storageBytes is in a stable state or it is being adjusted as a result of shared storage reallocation. This status can either be UPDATING, meaning the size of the snapshot is being updated, or UP_TO_DATE, meaning the size of the snapshot is up-to-date.",
|
| "enum": [
|
| "UPDATING",
|
| "UP_TO_DATE"
|
| @@ -12952,6 +12983,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -12981,6 +13013,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -12990,7 +13023,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -13054,7 +13087,7 @@
|
| "type": "string"
|
| },
|
| "name": {
|
| - "description": "Name of the resource; provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| + "description": "Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "type": "string"
|
| },
|
| @@ -13086,7 +13119,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#targetHttpProxyList",
|
| - "description": "Type of resource. Always compute#targetHttpProxyList for lists of Target HTTP proxies.",
|
| + "description": "Type of resource. Always compute#targetHttpProxyList for lists of target HTTP proxies.",
|
| "type": "string"
|
| },
|
| "nextPageToken": {
|
| @@ -13104,7 +13137,7 @@
|
| "id": "TargetHttpsProxiesSetSslCertificatesRequest",
|
| "properties": {
|
| "sslCertificates": {
|
| - "description": "New set of URLs to SslCertificate resources to associate with this TargetHttpProxy. Currently exactly one ssl certificate must be specified.",
|
| + "description": "New set of SslCertificate resources to associate with this TargetHttpsProxy resource. Currently exactly one SslCertificate resource must be specified.",
|
| "items": {
|
| "type": "string"
|
| },
|
| @@ -13132,7 +13165,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#targetHttpsProxy",
|
| - "description": "[Output Only] Type of the resource. Always compute#targetHttpsProxy for target HTTPS proxies.",
|
| + "description": "[Output Only] Type of resource. Always compute#targetHttpsProxy for target HTTPS proxies.",
|
| "type": "string"
|
| },
|
| "name": {
|
| @@ -13145,14 +13178,14 @@
|
| "type": "string"
|
| },
|
| "sslCertificates": {
|
| - "description": "URLs to SslCertificate resources that are used to authenticate connections between users and the load balancer. Currently exactly one SSL certificate must be specified.",
|
| + "description": "URLs to SslCertificate resources that are used to authenticate connections between users and the load balancer. Currently, exactly one SSL certificate must be specified.",
|
| "items": {
|
| "type": "string"
|
| },
|
| "type": "array"
|
| },
|
| "urlMap": {
|
| - "description": "URL to the UrlMap resource that defines the mapping from URL to the BackendService.",
|
| + "description": "A fully-qualified or valid partial URL to the UrlMap resource that defines the mapping from URL to the BackendService. For example, the following are all valid URLs for specifying a URL map: \n- https://www.googleapis.compute/v1/projects/project/global/urlMaps/url-map \n- projects/project/global/urlMaps/url-map \n- global/urlMaps/url-map",
|
| "type": "string"
|
| }
|
| },
|
| @@ -13175,7 +13208,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#targetHttpsProxyList",
|
| - "description": "Type of resource.",
|
| + "description": "Type of resource. Always compute#targetHttpsProxyList for lists of target HTTPS proxies.",
|
| "type": "string"
|
| },
|
| "nextPageToken": {
|
| @@ -13207,7 +13240,7 @@
|
| "type": "string"
|
| },
|
| "instance": {
|
| - "description": "The URL to the instance that terminates the relevant traffic.",
|
| + "description": "A URL to the virtual machine instance that handles traffic for this target instance. When creating a target instance, you can provide the fully-qualified URL or a valid partial URL to the desired virtual machine. For example, the following are all valid URLs: \n- https://www.googleapis.com/compute/v1/projects/project/zones/zone/instances/instance \n- projects/project/zones/zone/instances/instance \n- zones/zone/instances/instance",
|
| "type": "string"
|
| },
|
| "kind": {
|
| @@ -13319,6 +13352,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -13348,6 +13382,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -13357,7 +13392,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -13380,7 +13415,7 @@
|
| "type": "object"
|
| },
|
| "TargetPool": {
|
| - "description": "A TargetPool resource. This resource defines a pool of instances, associated HttpHealthCheck resources, and the fallback TargetPool.",
|
| + "description": "A TargetPool resource. This resource defines a pool of instances, associated HttpHealthCheck resources, and the fallback target pool.",
|
| "id": "TargetPool",
|
| "properties": {
|
| "backupPool": {
|
| @@ -13413,7 +13448,7 @@
|
| "type": "string"
|
| },
|
| "instances": {
|
| - "description": "A list of resource URLs to the member virtual machines serving this pool. They must live in zones contained in the same region as this pool.",
|
| + "description": "A list of resource URLs to the virtual machine instances serving this pool. They must live in zones contained in the same region as this pool.",
|
| "items": {
|
| "type": "string"
|
| },
|
| @@ -13466,12 +13501,12 @@
|
| "$ref": "TargetPoolsScopedList",
|
| "description": "Name of the scope containing this set of target pools."
|
| },
|
| - "description": "A map of scoped target pool lists.",
|
| + "description": "[Output Only] A map of scoped target pool lists.",
|
| "type": "object"
|
| },
|
| "kind": {
|
| "default": "compute#targetPoolAggregatedList",
|
| - "description": "Type of resource.",
|
| + "description": "[Output Only] Type of resource. Always compute#targetPoolAggregatedList for aggregated lists of target pools.",
|
| "type": "string"
|
| },
|
| "nextPageToken": {
|
| @@ -13496,7 +13531,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#targetPoolInstanceHealth",
|
| - "description": "Type of resource.",
|
| + "description": "[Output Only] Type of resource. Always compute#targetPoolInstanceHealth when checking the health of an instance.",
|
| "type": "string"
|
| }
|
| },
|
| @@ -13519,7 +13554,7 @@
|
| },
|
| "kind": {
|
| "default": "compute#targetPoolList",
|
| - "description": "Type of resource.",
|
| + "description": "[Output Only] Type of resource. Always compute#targetPoolList for lists of target pools.",
|
| "type": "string"
|
| },
|
| "nextPageToken": {
|
| @@ -13537,7 +13572,7 @@
|
| "id": "TargetPoolsAddHealthCheckRequest",
|
| "properties": {
|
| "healthChecks": {
|
| - "description": "Health check URLs to be added to targetPool.",
|
| + "description": "A list of HttpHealthCheck resources to add to the target pool.",
|
| "items": {
|
| "$ref": "HealthCheckReference"
|
| },
|
| @@ -13550,7 +13585,7 @@
|
| "id": "TargetPoolsAddInstanceRequest",
|
| "properties": {
|
| "instances": {
|
| - "description": "URLs of the instances to be added to targetPool.",
|
| + "description": "A full or partial URL to an instance to add to this target pool. This can be a full or partial URL. For example, the following are valid URLs: \n- https://www.googleapis.com/compute/v1/projects/project-id/zones/zone/instances/instance-name \n- projects/project-id/zones/zone/instances/instance-name \n- zones/zone/instances/instance-name",
|
| "items": {
|
| "$ref": "InstanceReference"
|
| },
|
| @@ -13563,7 +13598,7 @@
|
| "id": "TargetPoolsRemoveHealthCheckRequest",
|
| "properties": {
|
| "healthChecks": {
|
| - "description": "Health check URLs to be removed from targetPool.",
|
| + "description": "Health check URL to be removed. This can be a full or valid partial URL. For example, the following are valid URLs: \n- https://www.googleapis.com/compute/beta/projects/project/global/httpHealthChecks/health-check \n- projects/project/global/httpHealthChecks/health-check \n- global/httpHealthChecks/health-check",
|
| "items": {
|
| "$ref": "HealthCheckReference"
|
| },
|
| @@ -13576,7 +13611,7 @@
|
| "id": "TargetPoolsRemoveInstanceRequest",
|
| "properties": {
|
| "instances": {
|
| - "description": "URLs of the instances to be removed from targetPool.",
|
| + "description": "URLs of the instances to be removed from target pool.",
|
| "items": {
|
| "$ref": "InstanceReference"
|
| },
|
| @@ -13601,6 +13636,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -13630,6 +13666,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -13639,7 +13676,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -13671,6 +13708,7 @@
|
| "type": "object"
|
| },
|
| "TargetVpnGateway": {
|
| + "description": "Represents a Target VPN gateway resource.",
|
| "id": "TargetVpnGateway",
|
| "properties": {
|
| "creationTimestamp": {
|
| @@ -13704,7 +13742,7 @@
|
| "compute.targetVpnGateways.insert"
|
| ]
|
| },
|
| - "description": "Name of the resource; provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| + "description": "Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "type": "string"
|
| },
|
| @@ -13742,7 +13780,7 @@
|
| "type": "string"
|
| },
|
| "tunnels": {
|
| - "description": "[Output Only] A list of URLs to VpnTunnel resources. VpnTunnels are created using compute.vpntunnels.insert and associated to a VPN gateway.",
|
| + "description": "[Output Only] A list of URLs to VpnTunnel resources. VpnTunnels are created using compute.vpntunnels.insert method and associated to a VPN gateway.",
|
| "items": {
|
| "type": "string"
|
| },
|
| @@ -13761,7 +13799,7 @@
|
| "items": {
|
| "additionalProperties": {
|
| "$ref": "TargetVpnGatewaysScopedList",
|
| - "description": "[Output Only] Name of the scope containing this set of target vpn gateways."
|
| + "description": "[Output Only] Name of the scope containing this set of target VPN gateways."
|
| },
|
| "description": "A map of scoped target vpn gateway lists.",
|
| "type": "object"
|
| @@ -13829,6 +13867,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -13858,6 +13897,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -13867,7 +13907,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
| @@ -14138,7 +14178,7 @@
|
| "compute.vpnTunnels.insert"
|
| ]
|
| },
|
| - "description": "Name of the resource; provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| + "description": "Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.",
|
| "pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
| "type": "string"
|
| },
|
| @@ -14165,6 +14205,7 @@
|
| "status": {
|
| "description": "[Output Only] The status of the VPN tunnel.",
|
| "enum": [
|
| + "ALLOCATING_RESOURCES",
|
| "AUTHORIZATION_ERROR",
|
| "DEPROVISIONING",
|
| "ESTABLISHED",
|
| @@ -14188,6 +14229,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -14198,7 +14240,7 @@
|
| "compute.vpnTunnels.insert"
|
| ]
|
| },
|
| - "description": "URL of the VPN gateway to which this VPN tunnel is associated. Provided by the client when the VPN tunnel is created.",
|
| + "description": "URL of the VPN gateway with which this VPN tunnel is associated. Provided by the client when the VPN tunnel is created.",
|
| "type": "string"
|
| }
|
| },
|
| @@ -14282,6 +14324,7 @@
|
| "code": {
|
| "description": "[Output Only] A warning code, if applicable. For example, Compute Engine returns NO_RESULTS_ON_PAGE if there are no results in the response.",
|
| "enum": [
|
| + "CLEANUP_FAILED",
|
| "DEPRECATED_RESOURCE_USED",
|
| "DISK_SIZE_LARGER_THAN_IMAGE_SIZE",
|
| "INJECTED_KERNELS_DEPRECATED",
|
| @@ -14311,6 +14354,7 @@
|
| "",
|
| "",
|
| "",
|
| + "",
|
| ""
|
| ],
|
| "type": "string"
|
| @@ -14320,7 +14364,7 @@
|
| "items": {
|
| "properties": {
|
| "key": {
|
| - "description": "[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).",
|
| + "description": "[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).",
|
| "type": "string"
|
| },
|
| "value": {
|
|
|
Chromium Code Reviews
Issue 1797933002:
Api-roll 33: 2016-03-14 (Closed)
Base URL: git@github.com:dart-lang/googleapis.git@master