forked from TrueCloudLab/rclone
vendor: update all dependencies
This commit is contained in:
Nick Craig-Wood
parent
0b6fba34a3
commit
eb87cf6f12
2008 changed files with 352633 additions and 1004750 deletions
66
vendor/google.golang.org/api/deploymentmanager/v0.alpha/deploymentmanager-api.json
generated
vendored
66
vendor/google.golang.org/api/deploymentmanager/v0.alpha/deploymentmanager-api.json
generated
vendored
|
|
@ -1,12 +1,12 @@
|
|||
{
|
||||
"kind": "discovery#restDescription",
|
||||
"etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/J7uWrOuR-hj54j7lMEiUmNtWPRc\"",
|
||||
"etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/DSQnXnJrdGCXbfLjaO33fHf1TP4\"",
|
||||
"discoveryVersion": "v1",
|
||||
"id": "deploymentmanager:alpha",
|
||||
"name": "deploymentmanager",
|
||||
"canonicalName": "Deployment Manager Alpha",
|
||||
"version": "alpha",
|
||||
"revision": "20170501",
|
||||
"revision": "20170615",
|
||||
"title": "Google Cloud Deployment Manager Alpha API",
|
||||
"description": "The Deployment Manager API allows users to declaratively configure, deploy and run complex solutions on the Google Cloud Platform.",
|
||||
"ownerDomain": "google.com",
|
||||
|
|
@ -147,9 +147,13 @@
|
|||
"type": "object",
|
||||
"description": "Associates `members` with a `role`.",
|
||||
"properties": {
|
||||
"condition": {
|
||||
"$ref": "Expr",
|
||||
"description": "The condition that is associated with this binding. NOTE: an unsatisfied condition will not allow user access via current binding. Different bindings, including their conditions, are examined independently. This field is GOOGLE_INTERNAL."
|
||||
},
|
||||
"members": {
|
||||
"type": "array",
|
||||
"description": "Specifies the identities requesting access for a Cloud Platform resource. `members` can have the following values:\n\n* `allUsers`: A special identifier that represents anyone who is on the internet; with or without a Google account.\n\n* `allAuthenticatedUsers`: A special identifier that represents anyone who is authenticated with a Google account or a service account.\n\n* `user:{emailid}`: An email address that represents a specific Google account. For example, `alice@gmail.com` or `joe@example.com`.\n\n\n\n* `serviceAccount:{emailid}`: An email address that represents a service account. For example, `my-other-app@appspot.gserviceaccount.com`.\n\n* `group:{emailid}`: An email address that represents a Google group. For example, `admins@example.com`.\n\n* `domain:{domain}`: A Google Apps domain name that represents all the users of that domain. For example, `google.com` or `example.com`.",
|
||||
"description": "Specifies the identities requesting access for a Cloud Platform resource. `members` can have the following values:\n\n* `allUsers`: A special identifier that represents anyone who is on the internet; with or without a Google account.\n\n* `allAuthenticatedUsers`: A special identifier that represents anyone who is authenticated with a Google account or a service account.\n\n* `user:{emailid}`: An email address that represents a specific Google account. For example, `alice@gmail.com` or `joe@example.com`.\n\n\n\n* `serviceAccount:{emailid}`: An email address that represents a service account. For example, `my-other-app@appspot.gserviceaccount.com`.\n\n* `group:{emailid}`: An email address that represents a Google group. For example, `admins@example.com`.\n\n\n\n* `domain:{domain}`: A Google Apps domain name that represents all the users of that domain. For example, `google.com` or `example.com`.",
|
||||
"items": {
|
||||
"type": "string"
|
||||
}
|
||||
|
|
@ -477,6 +481,29 @@
|
|||
}
|
||||
}
|
||||
},
|
||||
"Expr": {
|
||||
"id": "Expr",
|
||||
"type": "object",
|
||||
"description": "Represents an expression text. Example:\n\ntitle: \"User account presence\" description: \"Determines whether the request has a user account\" expression: \"size(request.user) \u003e 0\"",
|
||||
"properties": {
|
||||
"description": {
|
||||
"type": "string",
|
||||
"description": "An optional description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI."
|
||||
},
|
||||
"expression": {
|
||||
"type": "string",
|
||||
"description": "Textual representation of an expression in Common Expression Language syntax.\n\nThe application context of the containing message determines which well-known feature set of CEL is supported."
|
||||
},
|
||||
"location": {
|
||||
"type": "string",
|
||||
"description": "An optional string indicating the location of the expression for error reporting, e.g. a file name and a position in the file."
|
||||
},
|
||||
"title": {
|
||||
"type": "string",
|
||||
"description": "An optional title for the expression, i.e. a short string describing its purpose. This can be used e.g. in UIs which allow to enter the expression."
|
||||
}
|
||||
}
|
||||
},
|
||||
"ImportFile": {
|
||||
"id": "ImportFile",
|
||||
"type": "object",
|
||||
|
|
@ -520,12 +547,27 @@
|
|||
"type": "object",
|
||||
"description": "Specifies what kind of log the caller must write",
|
||||
"properties": {
|
||||
"cloudAudit": {
|
||||
"$ref": "LogConfigCloudAuditOptions",
|
||||
"description": "Cloud audit options."
|
||||
},
|
||||
"counter": {
|
||||
"$ref": "LogConfigCounterOptions",
|
||||
"description": "Counter options."
|
||||
}
|
||||
}
|
||||
},
|
||||
"LogConfigCloudAuditOptions": {
|
||||
"id": "LogConfigCloudAuditOptions",
|
||||
"type": "object",
|
||||
"description": "Write a Cloud Audit log",
|
||||
"properties": {
|
||||
"logName": {
|
||||
"type": "string",
|
||||
"description": "The log_name to populate in the Cloud Audit Record."
|
||||
}
|
||||
}
|
||||
},
|
||||
"LogConfigCounterOptions": {
|
||||
"id": "LogConfigCounterOptions",
|
||||
"type": "object",
|
||||
|
|
@ -813,7 +855,7 @@
|
|||
},
|
||||
"bindings": {
|
||||
"type": "array",
|
||||
"description": "Associates a list of `members` to a `role`. Multiple `bindings` must not be specified for the same `role`. `bindings` with no members will result in an error.",
|
||||
"description": "Associates a list of `members` to a `role`. `bindings` with no members will result in an error.",
|
||||
"items": {
|
||||
"$ref": "Binding"
|
||||
}
|
||||
|
|
@ -1521,7 +1563,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -1831,7 +1873,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2183,7 +2225,7 @@
|
|||
},
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2272,7 +2314,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2375,7 +2417,7 @@
|
|||
},
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2568,7 +2610,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2618,7 +2660,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2848,7 +2890,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
|
|||
188
vendor/google.golang.org/api/deploymentmanager/v0.alpha/deploymentmanager-gen.go
generated
vendored
188
vendor/google.golang.org/api/deploymentmanager/v0.alpha/deploymentmanager-gen.go
generated
vendored
|
|
@ -299,6 +299,12 @@ func (s *BasicAuth) MarshalJSON() ([]byte, error) {
|
|||
|
||||
// Binding: Associates `members` with a `role`.
|
||||
type Binding struct {
|
||||
// Condition: The condition that is associated with this binding. NOTE:
|
||||
// an unsatisfied condition will not allow user access via current
|
||||
// binding. Different bindings, including their conditions, are examined
|
||||
// independently. This field is GOOGLE_INTERNAL.
|
||||
Condition *Expr `json:"condition,omitempty"`
|
||||
|
||||
// Members: Specifies the identities requesting access for a Cloud
|
||||
// Platform resource. `members` can have the following values:
|
||||
//
|
||||
|
|
@ -322,6 +328,8 @@ type Binding struct {
|
|||
// * `group:{emailid}`: An email address that represents a Google group.
|
||||
// For example, `admins@example.com`.
|
||||
//
|
||||
//
|
||||
//
|
||||
// * `domain:{domain}`: A Google Apps domain name that represents all
|
||||
// the users of that domain. For example, `google.com` or `example.com`.
|
||||
Members []string `json:"members,omitempty"`
|
||||
|
|
@ -330,7 +338,7 @@ type Binding struct {
|
|||
// `roles/viewer`, `roles/editor`, or `roles/owner`.
|
||||
Role string `json:"role,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "Members") to
|
||||
// ForceSendFields is a list of field names (e.g. "Condition") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
|
|
@ -338,7 +346,7 @@ type Binding struct {
|
|||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "Members") to include in
|
||||
// NullFields is a list of field names (e.g. "Condition") to include in
|
||||
// API requests with the JSON null value. By default, fields with empty
|
||||
// values are omitted from API requests. However, any field with an
|
||||
// empty value appearing in NullFields will be sent to the server as
|
||||
|
|
@ -953,6 +961,56 @@ func (s *DeploymentsStopRequest) MarshalJSON() ([]byte, error) {
|
|||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
// Expr: Represents an expression text. Example:
|
||||
//
|
||||
// title: "User account presence" description: "Determines whether the
|
||||
// request has a user account" expression: "size(request.user) > 0"
|
||||
type Expr struct {
|
||||
// Description: An optional description of the expression. This is a
|
||||
// longer text which describes the expression, e.g. when hovered over it
|
||||
// in a UI.
|
||||
Description string `json:"description,omitempty"`
|
||||
|
||||
// Expression: Textual representation of an expression in Common
|
||||
// Expression Language syntax.
|
||||
//
|
||||
// The application context of the containing message determines which
|
||||
// well-known feature set of CEL is supported.
|
||||
Expression string `json:"expression,omitempty"`
|
||||
|
||||
// Location: An optional string indicating the location of the
|
||||
// expression for error reporting, e.g. a file name and a position in
|
||||
// the file.
|
||||
Location string `json:"location,omitempty"`
|
||||
|
||||
// Title: An optional title for the expression, i.e. a short string
|
||||
// describing its purpose. This can be used e.g. in UIs which allow to
|
||||
// enter the expression.
|
||||
Title string `json:"title,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "Description") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
// server regardless of whether the field is empty or not. This may be
|
||||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "Description") to include
|
||||
// in API requests with the JSON null value. By default, fields with
|
||||
// empty values are omitted from API requests. However, any field with
|
||||
// an empty value appearing in NullFields will be sent to the server as
|
||||
// null. It is an error if a field in this list has a non-empty value.
|
||||
// This may be used to include null fields in Patch requests.
|
||||
NullFields []string `json:"-"`
|
||||
}
|
||||
|
||||
func (s *Expr) MarshalJSON() ([]byte, error) {
|
||||
type noMethod Expr
|
||||
raw := noMethod(*s)
|
||||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
type ImportFile struct {
|
||||
// Content: The contents of the file.
|
||||
Content string `json:"content,omitempty"`
|
||||
|
|
@ -1024,10 +1082,13 @@ func (s *InputMapping) MarshalJSON() ([]byte, error) {
|
|||
|
||||
// LogConfig: Specifies what kind of log the caller must write
|
||||
type LogConfig struct {
|
||||
// CloudAudit: Cloud audit options.
|
||||
CloudAudit *LogConfigCloudAuditOptions `json:"cloudAudit,omitempty"`
|
||||
|
||||
// Counter: Counter options.
|
||||
Counter *LogConfigCounterOptions `json:"counter,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "Counter") to
|
||||
// ForceSendFields is a list of field names (e.g. "CloudAudit") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
|
|
@ -1035,7 +1096,7 @@ type LogConfig struct {
|
|||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "Counter") to include in
|
||||
// NullFields is a list of field names (e.g. "CloudAudit") to include in
|
||||
// API requests with the JSON null value. By default, fields with empty
|
||||
// values are omitted from API requests. However, any field with an
|
||||
// empty value appearing in NullFields will be sent to the server as
|
||||
|
|
@ -1050,6 +1111,34 @@ func (s *LogConfig) MarshalJSON() ([]byte, error) {
|
|||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
// LogConfigCloudAuditOptions: Write a Cloud Audit log
|
||||
type LogConfigCloudAuditOptions struct {
|
||||
// LogName: The log_name to populate in the Cloud Audit Record.
|
||||
LogName string `json:"logName,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "LogName") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
// server regardless of whether the field is empty or not. This may be
|
||||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "LogName") to include in
|
||||
// API requests with the JSON null value. By default, fields with empty
|
||||
// values are omitted from API requests. However, any field with an
|
||||
// empty value appearing in NullFields will be sent to the server as
|
||||
// null. It is an error if a field in this list has a non-empty value.
|
||||
// This may be used to include null fields in Patch requests.
|
||||
NullFields []string `json:"-"`
|
||||
}
|
||||
|
||||
func (s *LogConfigCloudAuditOptions) MarshalJSON() ([]byte, error) {
|
||||
type noMethod LogConfigCloudAuditOptions
|
||||
raw := noMethod(*s)
|
||||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
// LogConfigCounterOptions: Options for counters
|
||||
type LogConfigCounterOptions struct {
|
||||
// Field: The field value to attribute.
|
||||
|
|
@ -1540,8 +1629,7 @@ type Policy struct {
|
|||
// policy.
|
||||
AuditConfigs []*AuditConfig `json:"auditConfigs,omitempty"`
|
||||
|
||||
// Bindings: Associates a list of `members` to a `role`. Multiple
|
||||
// `bindings` must not be specified for the same `role`. `bindings` with
|
||||
// Bindings: Associates a list of `members` to a `role`. `bindings` with
|
||||
// no members will result in an error.
|
||||
Bindings []*Binding `json:"bindings,omitempty"`
|
||||
|
||||
|
|
@ -3061,10 +3149,9 @@ func (r *CompositeTypesService) List(project string) *CompositeTypesListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -3076,7 +3163,7 @@ func (r *CompositeTypesService) List(project string) *CompositeTypesListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -3231,7 +3318,7 @@ func (c *CompositeTypesListCall) Do(opts ...googleapi.CallOption) (*CompositeTyp
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -4374,10 +4461,9 @@ func (r *DeploymentsService) List(project string) *DeploymentsListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -4389,7 +4475,7 @@ func (r *DeploymentsService) List(project string) *DeploymentsListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -4544,7 +4630,7 @@ func (c *DeploymentsListCall) Do(opts ...googleapi.CallOption) (*DeploymentsList
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -5672,10 +5758,9 @@ func (r *ManifestsService) List(project string, deployment string) *ManifestsLis
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -5687,7 +5772,7 @@ func (r *ManifestsService) List(project string, deployment string) *ManifestsLis
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -5851,7 +5936,7 @@ func (c *ManifestsListCall) Do(opts ...googleapi.CallOption) (*ManifestsListResp
|
|||
// "type": "string"
|
||||
// },
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -6085,10 +6170,9 @@ func (r *OperationsService) List(project string) *OperationsListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -6100,7 +6184,7 @@ func (r *OperationsService) List(project string) *OperationsListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -6255,7 +6339,7 @@ func (c *OperationsListCall) Do(opts ...googleapi.CallOption) (*OperationsListRe
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -6502,10 +6586,9 @@ func (r *ResourcesService) List(project string, deployment string) *ResourcesLis
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -6517,7 +6600,7 @@ func (r *ResourcesService) List(project string, deployment string) *ResourcesLis
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -6681,7 +6764,7 @@ func (c *ResourcesListCall) Do(opts ...googleapi.CallOption) (*ResourcesListResp
|
|||
// "type": "string"
|
||||
// },
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -7349,10 +7432,9 @@ func (r *TypeProvidersService) List(project string) *TypeProvidersListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -7364,7 +7446,7 @@ func (r *TypeProvidersService) List(project string) *TypeProvidersListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -7519,7 +7601,7 @@ func (c *TypeProvidersListCall) Do(opts ...googleapi.CallOption) (*TypeProviders
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -7604,10 +7686,9 @@ func (r *TypeProvidersService) ListTypes(project string, typeProvider string) *T
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -7619,7 +7700,7 @@ func (r *TypeProvidersService) ListTypes(project string, typeProvider string) *T
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -7776,7 +7857,7 @@ func (c *TypeProvidersListTypesCall) Do(opts ...googleapi.CallOption) (*TypeProv
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -8581,10 +8662,9 @@ func (r *TypesService) List(project string) *TypesListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -8596,7 +8676,7 @@ func (r *TypesService) List(project string) *TypesListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -8751,7 +8831,7 @@ func (c *TypesListCall) Do(opts ...googleapi.CallOption) (*TypesListResponse, er
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
|
|||
60
vendor/google.golang.org/api/deploymentmanager/v2/deploymentmanager-api.json
generated
vendored
60
vendor/google.golang.org/api/deploymentmanager/v2/deploymentmanager-api.json
generated
vendored
|
|
@ -1,12 +1,12 @@
|
|||
{
|
||||
"kind": "discovery#restDescription",
|
||||
"etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/llynIIguUtQGZnafw0-LKyjVFvE\"",
|
||||
"etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/D9oyxr4DnVbupMt9dSmNXQp4YGQ\"",
|
||||
"discoveryVersion": "v1",
|
||||
"id": "deploymentmanager:v2",
|
||||
"name": "deploymentmanager",
|
||||
"canonicalName": "Deployment Manager",
|
||||
"version": "v2",
|
||||
"revision": "20170501",
|
||||
"revision": "20170615",
|
||||
"title": "Google Cloud Deployment Manager API",
|
||||
"description": "Declares, configures, and deploys complex solutions on Google Cloud Platform.",
|
||||
"ownerDomain": "google.com",
|
||||
|
|
@ -134,9 +134,13 @@
|
|||
"type": "object",
|
||||
"description": "Associates `members` with a `role`.",
|
||||
"properties": {
|
||||
"condition": {
|
||||
"$ref": "Expr",
|
||||
"description": "The condition that is associated with this binding. NOTE: an unsatisfied condition will not allow user access via current binding. Different bindings, including their conditions, are examined independently. This field is GOOGLE_INTERNAL."
|
||||
},
|
||||
"members": {
|
||||
"type": "array",
|
||||
"description": "Specifies the identities requesting access for a Cloud Platform resource. `members` can have the following values:\n\n* `allUsers`: A special identifier that represents anyone who is on the internet; with or without a Google account.\n\n* `allAuthenticatedUsers`: A special identifier that represents anyone who is authenticated with a Google account or a service account.\n\n* `user:{emailid}`: An email address that represents a specific Google account. For example, `alice@gmail.com` or `joe@example.com`.\n\n\n\n* `serviceAccount:{emailid}`: An email address that represents a service account. For example, `my-other-app@appspot.gserviceaccount.com`.\n\n* `group:{emailid}`: An email address that represents a Google group. For example, `admins@example.com`.\n\n* `domain:{domain}`: A Google Apps domain name that represents all the users of that domain. For example, `google.com` or `example.com`.",
|
||||
"description": "Specifies the identities requesting access for a Cloud Platform resource. `members` can have the following values:\n\n* `allUsers`: A special identifier that represents anyone who is on the internet; with or without a Google account.\n\n* `allAuthenticatedUsers`: A special identifier that represents anyone who is authenticated with a Google account or a service account.\n\n* `user:{emailid}`: An email address that represents a specific Google account. For example, `alice@gmail.com` or `joe@example.com`.\n\n\n\n* `serviceAccount:{emailid}`: An email address that represents a service account. For example, `my-other-app@appspot.gserviceaccount.com`.\n\n* `group:{emailid}`: An email address that represents a Google group. For example, `admins@example.com`.\n\n\n\n* `domain:{domain}`: A Google Apps domain name that represents all the users of that domain. For example, `google.com` or `example.com`.",
|
||||
"items": {
|
||||
"type": "string"
|
||||
}
|
||||
|
|
@ -336,6 +340,29 @@
|
|||
}
|
||||
}
|
||||
},
|
||||
"Expr": {
|
||||
"id": "Expr",
|
||||
"type": "object",
|
||||
"description": "Represents an expression text. Example:\n\ntitle: \"User account presence\" description: \"Determines whether the request has a user account\" expression: \"size(request.user) \u003e 0\"",
|
||||
"properties": {
|
||||
"description": {
|
||||
"type": "string",
|
||||
"description": "An optional description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI."
|
||||
},
|
||||
"expression": {
|
||||
"type": "string",
|
||||
"description": "Textual representation of an expression in Common Expression Language syntax.\n\nThe application context of the containing message determines which well-known feature set of CEL is supported."
|
||||
},
|
||||
"location": {
|
||||
"type": "string",
|
||||
"description": "An optional string indicating the location of the expression for error reporting, e.g. a file name and a position in the file."
|
||||
},
|
||||
"title": {
|
||||
"type": "string",
|
||||
"description": "An optional title for the expression, i.e. a short string describing its purpose. This can be used e.g. in UIs which allow to enter the expression."
|
||||
}
|
||||
}
|
||||
},
|
||||
"ImportFile": {
|
||||
"id": "ImportFile",
|
||||
"type": "object",
|
||||
|
|
@ -356,12 +383,27 @@
|
|||
"type": "object",
|
||||
"description": "Specifies what kind of log the caller must write",
|
||||
"properties": {
|
||||
"cloudAudit": {
|
||||
"$ref": "LogConfigCloudAuditOptions",
|
||||
"description": "Cloud audit options."
|
||||
},
|
||||
"counter": {
|
||||
"$ref": "LogConfigCounterOptions",
|
||||
"description": "Counter options."
|
||||
}
|
||||
}
|
||||
},
|
||||
"LogConfigCloudAuditOptions": {
|
||||
"id": "LogConfigCloudAuditOptions",
|
||||
"type": "object",
|
||||
"description": "Write a Cloud Audit log",
|
||||
"properties": {
|
||||
"logName": {
|
||||
"type": "string",
|
||||
"description": "The log_name to populate in the Cloud Audit Record."
|
||||
}
|
||||
}
|
||||
},
|
||||
"LogConfigCounterOptions": {
|
||||
"id": "LogConfigCounterOptions",
|
||||
"type": "object",
|
||||
|
|
@ -627,7 +669,7 @@
|
|||
},
|
||||
"bindings": {
|
||||
"type": "array",
|
||||
"description": "Associates a list of `members` to a `role`. Multiple `bindings` must not be specified for the same `role`. `bindings` with no members will result in an error.",
|
||||
"description": "Associates a list of `members` to a `role`. `bindings` with no members will result in an error.",
|
||||
"items": {
|
||||
"$ref": "Binding"
|
||||
}
|
||||
|
|
@ -1198,7 +1240,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -1550,7 +1592,7 @@
|
|||
},
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -1639,7 +1681,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -1742,7 +1784,7 @@
|
|||
},
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -1797,7 +1839,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
|
|||
155
vendor/google.golang.org/api/deploymentmanager/v2/deploymentmanager-gen.go
generated
vendored
155
vendor/google.golang.org/api/deploymentmanager/v2/deploymentmanager-gen.go
generated
vendored
|
|
@ -246,6 +246,12 @@ func (s *AuditLogConfig) MarshalJSON() ([]byte, error) {
|
|||
|
||||
// Binding: Associates `members` with a `role`.
|
||||
type Binding struct {
|
||||
// Condition: The condition that is associated with this binding. NOTE:
|
||||
// an unsatisfied condition will not allow user access via current
|
||||
// binding. Different bindings, including their conditions, are examined
|
||||
// independently. This field is GOOGLE_INTERNAL.
|
||||
Condition *Expr `json:"condition,omitempty"`
|
||||
|
||||
// Members: Specifies the identities requesting access for a Cloud
|
||||
// Platform resource. `members` can have the following values:
|
||||
//
|
||||
|
|
@ -269,6 +275,8 @@ type Binding struct {
|
|||
// * `group:{emailid}`: An email address that represents a Google group.
|
||||
// For example, `admins@example.com`.
|
||||
//
|
||||
//
|
||||
//
|
||||
// * `domain:{domain}`: A Google Apps domain name that represents all
|
||||
// the users of that domain. For example, `google.com` or `example.com`.
|
||||
Members []string `json:"members,omitempty"`
|
||||
|
|
@ -277,7 +285,7 @@ type Binding struct {
|
|||
// `roles/viewer`, `roles/editor`, or `roles/owner`.
|
||||
Role string `json:"role,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "Members") to
|
||||
// ForceSendFields is a list of field names (e.g. "Condition") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
|
|
@ -285,7 +293,7 @@ type Binding struct {
|
|||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "Members") to include in
|
||||
// NullFields is a list of field names (e.g. "Condition") to include in
|
||||
// API requests with the JSON null value. By default, fields with empty
|
||||
// values are omitted from API requests. However, any field with an
|
||||
// empty value appearing in NullFields will be sent to the server as
|
||||
|
|
@ -669,6 +677,56 @@ func (s *DeploymentsStopRequest) MarshalJSON() ([]byte, error) {
|
|||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
// Expr: Represents an expression text. Example:
|
||||
//
|
||||
// title: "User account presence" description: "Determines whether the
|
||||
// request has a user account" expression: "size(request.user) > 0"
|
||||
type Expr struct {
|
||||
// Description: An optional description of the expression. This is a
|
||||
// longer text which describes the expression, e.g. when hovered over it
|
||||
// in a UI.
|
||||
Description string `json:"description,omitempty"`
|
||||
|
||||
// Expression: Textual representation of an expression in Common
|
||||
// Expression Language syntax.
|
||||
//
|
||||
// The application context of the containing message determines which
|
||||
// well-known feature set of CEL is supported.
|
||||
Expression string `json:"expression,omitempty"`
|
||||
|
||||
// Location: An optional string indicating the location of the
|
||||
// expression for error reporting, e.g. a file name and a position in
|
||||
// the file.
|
||||
Location string `json:"location,omitempty"`
|
||||
|
||||
// Title: An optional title for the expression, i.e. a short string
|
||||
// describing its purpose. This can be used e.g. in UIs which allow to
|
||||
// enter the expression.
|
||||
Title string `json:"title,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "Description") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
// server regardless of whether the field is empty or not. This may be
|
||||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "Description") to include
|
||||
// in API requests with the JSON null value. By default, fields with
|
||||
// empty values are omitted from API requests. However, any field with
|
||||
// an empty value appearing in NullFields will be sent to the server as
|
||||
// null. It is an error if a field in this list has a non-empty value.
|
||||
// This may be used to include null fields in Patch requests.
|
||||
NullFields []string `json:"-"`
|
||||
}
|
||||
|
||||
func (s *Expr) MarshalJSON() ([]byte, error) {
|
||||
type noMethod Expr
|
||||
raw := noMethod(*s)
|
||||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
type ImportFile struct {
|
||||
// Content: The contents of the file.
|
||||
Content string `json:"content,omitempty"`
|
||||
|
|
@ -701,10 +759,13 @@ func (s *ImportFile) MarshalJSON() ([]byte, error) {
|
|||
|
||||
// LogConfig: Specifies what kind of log the caller must write
|
||||
type LogConfig struct {
|
||||
// CloudAudit: Cloud audit options.
|
||||
CloudAudit *LogConfigCloudAuditOptions `json:"cloudAudit,omitempty"`
|
||||
|
||||
// Counter: Counter options.
|
||||
Counter *LogConfigCounterOptions `json:"counter,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "Counter") to
|
||||
// ForceSendFields is a list of field names (e.g. "CloudAudit") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
|
|
@ -712,7 +773,7 @@ type LogConfig struct {
|
|||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "Counter") to include in
|
||||
// NullFields is a list of field names (e.g. "CloudAudit") to include in
|
||||
// API requests with the JSON null value. By default, fields with empty
|
||||
// values are omitted from API requests. However, any field with an
|
||||
// empty value appearing in NullFields will be sent to the server as
|
||||
|
|
@ -727,6 +788,34 @@ func (s *LogConfig) MarshalJSON() ([]byte, error) {
|
|||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
// LogConfigCloudAuditOptions: Write a Cloud Audit log
|
||||
type LogConfigCloudAuditOptions struct {
|
||||
// LogName: The log_name to populate in the Cloud Audit Record.
|
||||
LogName string `json:"logName,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "LogName") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
// server regardless of whether the field is empty or not. This may be
|
||||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "LogName") to include in
|
||||
// API requests with the JSON null value. By default, fields with empty
|
||||
// values are omitted from API requests. However, any field with an
|
||||
// empty value appearing in NullFields will be sent to the server as
|
||||
// null. It is an error if a field in this list has a non-empty value.
|
||||
// This may be used to include null fields in Patch requests.
|
||||
NullFields []string `json:"-"`
|
||||
}
|
||||
|
||||
func (s *LogConfigCloudAuditOptions) MarshalJSON() ([]byte, error) {
|
||||
type noMethod LogConfigCloudAuditOptions
|
||||
raw := noMethod(*s)
|
||||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
// LogConfigCounterOptions: Options for counters
|
||||
type LogConfigCounterOptions struct {
|
||||
// Field: The field value to attribute.
|
||||
|
|
@ -1179,8 +1268,7 @@ type Policy struct {
|
|||
// policy.
|
||||
AuditConfigs []*AuditConfig `json:"auditConfigs,omitempty"`
|
||||
|
||||
// Bindings: Associates a list of `members` to a `role`. Multiple
|
||||
// `bindings` must not be specified for the same `role`. `bindings` with
|
||||
// Bindings: Associates a list of `members` to a `role`. `bindings` with
|
||||
// no members will result in an error.
|
||||
Bindings []*Binding `json:"bindings,omitempty"`
|
||||
|
||||
|
|
@ -2660,10 +2748,9 @@ func (r *DeploymentsService) List(project string) *DeploymentsListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -2675,7 +2762,7 @@ func (r *DeploymentsService) List(project string) *DeploymentsListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -2830,7 +2917,7 @@ func (c *DeploymentsListCall) Do(opts ...googleapi.CallOption) (*DeploymentsList
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -3958,10 +4045,9 @@ func (r *ManifestsService) List(project string, deployment string) *ManifestsLis
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -3973,7 +4059,7 @@ func (r *ManifestsService) List(project string, deployment string) *ManifestsLis
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -4137,7 +4223,7 @@ func (c *ManifestsListCall) Do(opts ...googleapi.CallOption) (*ManifestsListResp
|
|||
// "type": "string"
|
||||
// },
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -4371,10 +4457,9 @@ func (r *OperationsService) List(project string) *OperationsListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -4386,7 +4471,7 @@ func (r *OperationsService) List(project string) *OperationsListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -4541,7 +4626,7 @@ func (c *OperationsListCall) Do(opts ...googleapi.CallOption) (*OperationsListRe
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -4788,10 +4873,9 @@ func (r *ResourcesService) List(project string, deployment string) *ResourcesLis
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -4803,7 +4887,7 @@ func (r *ResourcesService) List(project string, deployment string) *ResourcesLis
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -4967,7 +5051,7 @@ func (c *ResourcesListCall) Do(opts ...googleapi.CallOption) (*ResourcesListResp
|
|||
// "type": "string"
|
||||
// },
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -5050,10 +5134,9 @@ func (r *TypesService) List(project string) *TypesListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -5065,7 +5148,7 @@ func (r *TypesService) List(project string) *TypesListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -5220,7 +5303,7 @@ func (c *TypesListCall) Do(opts ...googleapi.CallOption) (*TypesListResponse, er
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
|
|||
66
vendor/google.golang.org/api/deploymentmanager/v2beta/deploymentmanager-api.json
generated
vendored
66
vendor/google.golang.org/api/deploymentmanager/v2beta/deploymentmanager-api.json
generated
vendored
|
|
@ -1,12 +1,12 @@
|
|||
{
|
||||
"kind": "discovery#restDescription",
|
||||
"etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/v0iGvBxOsg7NAep2sacazzshACc\"",
|
||||
"etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/BpAXxEaDX5Q7fHdBGIpwDxZQd84\"",
|
||||
"discoveryVersion": "v1",
|
||||
"id": "deploymentmanager:v2beta",
|
||||
"name": "deploymentmanager",
|
||||
"canonicalName": "Deployment Manager V2Beta",
|
||||
"version": "v2beta",
|
||||
"revision": "20170501",
|
||||
"revision": "20170615",
|
||||
"title": "Google Cloud Deployment Manager API V2Beta Methods",
|
||||
"description": "The Deployment Manager API allows users to declaratively configure, deploy and run complex solutions on the Google Cloud Platform.",
|
||||
"ownerDomain": "google.com",
|
||||
|
|
@ -173,9 +173,13 @@
|
|||
"type": "object",
|
||||
"description": "Associates `members` with a `role`.",
|
||||
"properties": {
|
||||
"condition": {
|
||||
"$ref": "Expr",
|
||||
"description": "The condition that is associated with this binding. NOTE: an unsatisfied condition will not allow user access via current binding. Different bindings, including their conditions, are examined independently. This field is GOOGLE_INTERNAL."
|
||||
},
|
||||
"members": {
|
||||
"type": "array",
|
||||
"description": "Specifies the identities requesting access for a Cloud Platform resource. `members` can have the following values:\n\n* `allUsers`: A special identifier that represents anyone who is on the internet; with or without a Google account.\n\n* `allAuthenticatedUsers`: A special identifier that represents anyone who is authenticated with a Google account or a service account.\n\n* `user:{emailid}`: An email address that represents a specific Google account. For example, `alice@gmail.com` or `joe@example.com`.\n\n\n\n* `serviceAccount:{emailid}`: An email address that represents a service account. For example, `my-other-app@appspot.gserviceaccount.com`.\n\n* `group:{emailid}`: An email address that represents a Google group. For example, `admins@example.com`.\n\n* `domain:{domain}`: A Google Apps domain name that represents all the users of that domain. For example, `google.com` or `example.com`.",
|
||||
"description": "Specifies the identities requesting access for a Cloud Platform resource. `members` can have the following values:\n\n* `allUsers`: A special identifier that represents anyone who is on the internet; with or without a Google account.\n\n* `allAuthenticatedUsers`: A special identifier that represents anyone who is authenticated with a Google account or a service account.\n\n* `user:{emailid}`: An email address that represents a specific Google account. For example, `alice@gmail.com` or `joe@example.com`.\n\n\n\n* `serviceAccount:{emailid}`: An email address that represents a service account. For example, `my-other-app@appspot.gserviceaccount.com`.\n\n* `group:{emailid}`: An email address that represents a Google group. For example, `admins@example.com`.\n\n\n\n* `domain:{domain}`: A Google Apps domain name that represents all the users of that domain. For example, `google.com` or `example.com`.",
|
||||
"items": {
|
||||
"type": "string"
|
||||
}
|
||||
|
|
@ -477,6 +481,29 @@
|
|||
}
|
||||
}
|
||||
},
|
||||
"Expr": {
|
||||
"id": "Expr",
|
||||
"type": "object",
|
||||
"description": "Represents an expression text. Example:\n\ntitle: \"User account presence\" description: \"Determines whether the request has a user account\" expression: \"size(request.user) \u003e 0\"",
|
||||
"properties": {
|
||||
"description": {
|
||||
"type": "string",
|
||||
"description": "An optional description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI."
|
||||
},
|
||||
"expression": {
|
||||
"type": "string",
|
||||
"description": "Textual representation of an expression in Common Expression Language syntax.\n\nThe application context of the containing message determines which well-known feature set of CEL is supported."
|
||||
},
|
||||
"location": {
|
||||
"type": "string",
|
||||
"description": "An optional string indicating the location of the expression for error reporting, e.g. a file name and a position in the file."
|
||||
},
|
||||
"title": {
|
||||
"type": "string",
|
||||
"description": "An optional title for the expression, i.e. a short string describing its purpose. This can be used e.g. in UIs which allow to enter the expression."
|
||||
}
|
||||
}
|
||||
},
|
||||
"ImportFile": {
|
||||
"id": "ImportFile",
|
||||
"type": "object",
|
||||
|
|
@ -520,12 +547,27 @@
|
|||
"type": "object",
|
||||
"description": "Specifies what kind of log the caller must write",
|
||||
"properties": {
|
||||
"cloudAudit": {
|
||||
"$ref": "LogConfigCloudAuditOptions",
|
||||
"description": "Cloud audit options."
|
||||
},
|
||||
"counter": {
|
||||
"$ref": "LogConfigCounterOptions",
|
||||
"description": "Counter options."
|
||||
}
|
||||
}
|
||||
},
|
||||
"LogConfigCloudAuditOptions": {
|
||||
"id": "LogConfigCloudAuditOptions",
|
||||
"type": "object",
|
||||
"description": "Write a Cloud Audit log",
|
||||
"properties": {
|
||||
"logName": {
|
||||
"type": "string",
|
||||
"description": "The log_name to populate in the Cloud Audit Record."
|
||||
}
|
||||
}
|
||||
},
|
||||
"LogConfigCounterOptions": {
|
||||
"id": "LogConfigCounterOptions",
|
||||
"type": "object",
|
||||
|
|
@ -813,7 +855,7 @@
|
|||
},
|
||||
"bindings": {
|
||||
"type": "array",
|
||||
"description": "Associates a list of `members` to a `role`. Multiple `bindings` must not be specified for the same `role`. `bindings` with no members will result in an error.",
|
||||
"description": "Associates a list of `members` to a `role`. `bindings` with no members will result in an error.",
|
||||
"items": {
|
||||
"$ref": "Binding"
|
||||
}
|
||||
|
|
@ -1521,7 +1563,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -1831,7 +1873,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2183,7 +2225,7 @@
|
|||
},
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2272,7 +2314,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2375,7 +2417,7 @@
|
|||
},
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2568,7 +2610,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2618,7 +2660,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
@ -2752,7 +2794,7 @@
|
|||
"parameters": {
|
||||
"filter": {
|
||||
"type": "string",
|
||||
"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\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
"location": "query"
|
||||
},
|
||||
"maxResults": {
|
||||
|
|
|
|||
188
vendor/google.golang.org/api/deploymentmanager/v2beta/deploymentmanager-gen.go
generated
vendored
188
vendor/google.golang.org/api/deploymentmanager/v2beta/deploymentmanager-gen.go
generated
vendored
|
|
@ -339,6 +339,12 @@ func (s *BasicAuth) MarshalJSON() ([]byte, error) {
|
|||
|
||||
// Binding: Associates `members` with a `role`.
|
||||
type Binding struct {
|
||||
// Condition: The condition that is associated with this binding. NOTE:
|
||||
// an unsatisfied condition will not allow user access via current
|
||||
// binding. Different bindings, including their conditions, are examined
|
||||
// independently. This field is GOOGLE_INTERNAL.
|
||||
Condition *Expr `json:"condition,omitempty"`
|
||||
|
||||
// Members: Specifies the identities requesting access for a Cloud
|
||||
// Platform resource. `members` can have the following values:
|
||||
//
|
||||
|
|
@ -362,6 +368,8 @@ type Binding struct {
|
|||
// * `group:{emailid}`: An email address that represents a Google group.
|
||||
// For example, `admins@example.com`.
|
||||
//
|
||||
//
|
||||
//
|
||||
// * `domain:{domain}`: A Google Apps domain name that represents all
|
||||
// the users of that domain. For example, `google.com` or `example.com`.
|
||||
Members []string `json:"members,omitempty"`
|
||||
|
|
@ -370,7 +378,7 @@ type Binding struct {
|
|||
// `roles/viewer`, `roles/editor`, or `roles/owner`.
|
||||
Role string `json:"role,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "Members") to
|
||||
// ForceSendFields is a list of field names (e.g. "Condition") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
|
|
@ -378,7 +386,7 @@ type Binding struct {
|
|||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "Members") to include in
|
||||
// NullFields is a list of field names (e.g. "Condition") to include in
|
||||
// API requests with the JSON null value. By default, fields with empty
|
||||
// values are omitted from API requests. However, any field with an
|
||||
// empty value appearing in NullFields will be sent to the server as
|
||||
|
|
@ -953,6 +961,56 @@ func (s *DeploymentsStopRequest) MarshalJSON() ([]byte, error) {
|
|||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
// Expr: Represents an expression text. Example:
|
||||
//
|
||||
// title: "User account presence" description: "Determines whether the
|
||||
// request has a user account" expression: "size(request.user) > 0"
|
||||
type Expr struct {
|
||||
// Description: An optional description of the expression. This is a
|
||||
// longer text which describes the expression, e.g. when hovered over it
|
||||
// in a UI.
|
||||
Description string `json:"description,omitempty"`
|
||||
|
||||
// Expression: Textual representation of an expression in Common
|
||||
// Expression Language syntax.
|
||||
//
|
||||
// The application context of the containing message determines which
|
||||
// well-known feature set of CEL is supported.
|
||||
Expression string `json:"expression,omitempty"`
|
||||
|
||||
// Location: An optional string indicating the location of the
|
||||
// expression for error reporting, e.g. a file name and a position in
|
||||
// the file.
|
||||
Location string `json:"location,omitempty"`
|
||||
|
||||
// Title: An optional title for the expression, i.e. a short string
|
||||
// describing its purpose. This can be used e.g. in UIs which allow to
|
||||
// enter the expression.
|
||||
Title string `json:"title,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "Description") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
// server regardless of whether the field is empty or not. This may be
|
||||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "Description") to include
|
||||
// in API requests with the JSON null value. By default, fields with
|
||||
// empty values are omitted from API requests. However, any field with
|
||||
// an empty value appearing in NullFields will be sent to the server as
|
||||
// null. It is an error if a field in this list has a non-empty value.
|
||||
// This may be used to include null fields in Patch requests.
|
||||
NullFields []string `json:"-"`
|
||||
}
|
||||
|
||||
func (s *Expr) MarshalJSON() ([]byte, error) {
|
||||
type noMethod Expr
|
||||
raw := noMethod(*s)
|
||||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
type ImportFile struct {
|
||||
// Content: The contents of the file.
|
||||
Content string `json:"content,omitempty"`
|
||||
|
|
@ -1024,10 +1082,13 @@ func (s *InputMapping) MarshalJSON() ([]byte, error) {
|
|||
|
||||
// LogConfig: Specifies what kind of log the caller must write
|
||||
type LogConfig struct {
|
||||
// CloudAudit: Cloud audit options.
|
||||
CloudAudit *LogConfigCloudAuditOptions `json:"cloudAudit,omitempty"`
|
||||
|
||||
// Counter: Counter options.
|
||||
Counter *LogConfigCounterOptions `json:"counter,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "Counter") to
|
||||
// ForceSendFields is a list of field names (e.g. "CloudAudit") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
|
|
@ -1035,7 +1096,7 @@ type LogConfig struct {
|
|||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "Counter") to include in
|
||||
// NullFields is a list of field names (e.g. "CloudAudit") to include in
|
||||
// API requests with the JSON null value. By default, fields with empty
|
||||
// values are omitted from API requests. However, any field with an
|
||||
// empty value appearing in NullFields will be sent to the server as
|
||||
|
|
@ -1050,6 +1111,34 @@ func (s *LogConfig) MarshalJSON() ([]byte, error) {
|
|||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
// LogConfigCloudAuditOptions: Write a Cloud Audit log
|
||||
type LogConfigCloudAuditOptions struct {
|
||||
// LogName: The log_name to populate in the Cloud Audit Record.
|
||||
LogName string `json:"logName,omitempty"`
|
||||
|
||||
// ForceSendFields is a list of field names (e.g. "LogName") to
|
||||
// unconditionally include in API requests. By default, fields with
|
||||
// empty values are omitted from API requests. However, any non-pointer,
|
||||
// non-interface field appearing in ForceSendFields will be sent to the
|
||||
// server regardless of whether the field is empty or not. This may be
|
||||
// used to include empty fields in Patch requests.
|
||||
ForceSendFields []string `json:"-"`
|
||||
|
||||
// NullFields is a list of field names (e.g. "LogName") to include in
|
||||
// API requests with the JSON null value. By default, fields with empty
|
||||
// values are omitted from API requests. However, any field with an
|
||||
// empty value appearing in NullFields will be sent to the server as
|
||||
// null. It is an error if a field in this list has a non-empty value.
|
||||
// This may be used to include null fields in Patch requests.
|
||||
NullFields []string `json:"-"`
|
||||
}
|
||||
|
||||
func (s *LogConfigCloudAuditOptions) MarshalJSON() ([]byte, error) {
|
||||
type noMethod LogConfigCloudAuditOptions
|
||||
raw := noMethod(*s)
|
||||
return gensupport.MarshalJSON(raw, s.ForceSendFields, s.NullFields)
|
||||
}
|
||||
|
||||
// LogConfigCounterOptions: Options for counters
|
||||
type LogConfigCounterOptions struct {
|
||||
// Field: The field value to attribute.
|
||||
|
|
@ -1545,8 +1634,7 @@ type Policy struct {
|
|||
// policy.
|
||||
AuditConfigs []*AuditConfig `json:"auditConfigs,omitempty"`
|
||||
|
||||
// Bindings: Associates a list of `members` to a `role`. Multiple
|
||||
// `bindings` must not be specified for the same `role`. `bindings` with
|
||||
// Bindings: Associates a list of `members` to a `role`. `bindings` with
|
||||
// no members will result in an error.
|
||||
Bindings []*Binding `json:"bindings,omitempty"`
|
||||
|
||||
|
|
@ -3060,10 +3148,9 @@ func (r *CompositeTypesService) List(project string) *CompositeTypesListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -3075,7 +3162,7 @@ func (r *CompositeTypesService) List(project string) *CompositeTypesListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -3230,7 +3317,7 @@ func (c *CompositeTypesListCall) Do(opts ...googleapi.CallOption) (*CompositeTyp
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -4373,10 +4460,9 @@ func (r *DeploymentsService) List(project string) *DeploymentsListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -4388,7 +4474,7 @@ func (r *DeploymentsService) List(project string) *DeploymentsListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -4543,7 +4629,7 @@ func (c *DeploymentsListCall) Do(opts ...googleapi.CallOption) (*DeploymentsList
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -5671,10 +5757,9 @@ func (r *ManifestsService) List(project string, deployment string) *ManifestsLis
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -5686,7 +5771,7 @@ func (r *ManifestsService) List(project string, deployment string) *ManifestsLis
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -5850,7 +5935,7 @@ func (c *ManifestsListCall) Do(opts ...googleapi.CallOption) (*ManifestsListResp
|
|||
// "type": "string"
|
||||
// },
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -6084,10 +6169,9 @@ func (r *OperationsService) List(project string) *OperationsListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -6099,7 +6183,7 @@ func (r *OperationsService) List(project string) *OperationsListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -6254,7 +6338,7 @@ func (c *OperationsListCall) Do(opts ...googleapi.CallOption) (*OperationsListRe
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -6501,10 +6585,9 @@ func (r *ResourcesService) List(project string, deployment string) *ResourcesLis
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -6516,7 +6599,7 @@ func (r *ResourcesService) List(project string, deployment string) *ResourcesLis
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -6680,7 +6763,7 @@ func (c *ResourcesListCall) Do(opts ...googleapi.CallOption) (*ResourcesListResp
|
|||
// "type": "string"
|
||||
// },
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -7348,10 +7431,9 @@ func (r *TypeProvidersService) List(project string) *TypeProvidersListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -7363,7 +7445,7 @@ func (r *TypeProvidersService) List(project string) *TypeProvidersListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -7518,7 +7600,7 @@ func (c *TypeProvidersListCall) Do(opts ...googleapi.CallOption) (*TypeProviders
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -7603,10 +7685,9 @@ func (r *TypeProvidersService) ListTypes(project string, typeProvider string) *T
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -7618,7 +7699,7 @@ func (r *TypeProvidersService) ListTypes(project string, typeProvider string) *T
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -7775,7 +7856,7 @@ func (c *TypeProvidersListTypesCall) Do(opts ...googleapi.CallOption) (*TypeProv
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
@ -8157,10 +8238,9 @@ func (r *TypesService) List(project string) *TypesListCall {
|
|||
return c
|
||||
}
|
||||
|
||||
// Filter sets the optional parameter "filter": 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.
|
||||
// Filter sets the optional parameter "filter": Sets a filter
|
||||
// {expression} for filtering listed resources. Your {expression} must
|
||||
// be in the format: field_name comparison_string literal_string.
|
||||
//
|
||||
// The field_name is the name of the field you want to compare. Only
|
||||
// atomic field types are supported (string, number, boolean). The
|
||||
|
|
@ -8172,7 +8252,7 @@ func (r *TypesService) List(project string) *TypesListCall {
|
|||
// match the entire field.
|
||||
//
|
||||
// For example, to filter for instances that do not have a name of
|
||||
// example-instance, you would use filter=name ne example-instance.
|
||||
// example-instance, you would use name ne example-instance.
|
||||
//
|
||||
// You can filter on nested fields. For example, you could filter on
|
||||
// instances that have set the scheduling.automaticRestart field to
|
||||
|
|
@ -8327,7 +8407,7 @@ func (c *TypesListCall) Do(opts ...googleapi.CallOption) (*TypesListResponse, er
|
|||
// ],
|
||||
// "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, to filter for instances that do not have a name of example-instance, you would use filter=name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "description": "Sets a filter {expression} for filtering listed resources. 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 name ne example-instance.\n\nYou can filter on nested fields. For example, you could filter on instances that have set the scheduling.automaticRestart field to true. Use filtering on nested fields to take advantage of labels to organize and search for results based on label values.\n\nTo filter on multiple expressions, provide each separate expression within parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-central1-f). Multiple expressions are treated as AND expressions, meaning that resources must match all expressions to pass the filters.",
|
||||
// "location": "query",
|
||||
// "type": "string"
|
||||
// },
|
||||
|
|
|
|||
883
vendor/google.golang.org/api/deploymentmanager/v2beta1/deploymentmanager-api.json
generated
vendored
883
vendor/google.golang.org/api/deploymentmanager/v2beta1/deploymentmanager-api.json
generated
vendored
|
|
@ -1,883 +0,0 @@
|
|||
{
|
||||
"kind": "discovery#restDescription",
|
||||
"etag": "\"ye6orv2F-1npMW3u9suM3a7C5Bo/u5FQM4I03EZTfBK_pxzZ11vNzAs\"",
|
||||
"discoveryVersion": "v1",
|
||||
"id": "deploymentmanager:v2beta1",
|
||||
"name": "deploymentmanager",
|
||||
"version": "v2beta1",
|
||||
"revision": "20150831",
|
||||
"title": "Google Cloud Deployment Manager API",
|
||||
"description": "The Deployment Manager API allows users to declaratively configure, deploy and run complex solutions on the Google Cloud Platform.",
|
||||
"ownerDomain": "google.com",
|
||||
"ownerName": "Google",
|
||||
"icons": {
|
||||
"x16": "http://www.google.com/images/icons/product/search-16.gif",
|
||||
"x32": "http://www.google.com/images/icons/product/search-32.gif"
|
||||
},
|
||||
"documentationLink": "https://developers.google.com/deployment-manager/",
|
||||
"labels": [
|
||||
"limited_availability"
|
||||
],
|
||||
"protocol": "rest",
|
||||
"baseUrl": "https://www.googleapis.com/deploymentmanager/v2beta1/projects/",
|
||||
"basePath": "/deploymentmanager/v2beta1/projects/",
|
||||
"rootUrl": "https://www.googleapis.com/",
|
||||
"servicePath": "deploymentmanager/v2beta1/projects/",
|
||||
"batchPath": "batch",
|
||||
"parameters": {
|
||||
"alt": {
|
||||
"type": "string",
|
||||
"description": "Data format for the response.",
|
||||
"default": "json",
|
||||
"enum": [
|
||||
"json"
|
||||
],
|
||||
"enumDescriptions": [
|
||||
"Responses with Content-Type of application/json"
|
||||
],
|
||||
"location": "query"
|
||||
},
|
||||
"fields": {
|
||||
"type": "string",
|
||||
"description": "Selector specifying which fields to include in a partial response.",
|
||||
"location": "query"
|
||||
},
|
||||
"key": {
|
||||
"type": "string",
|
||||
"description": "API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.",
|
||||
"location": "query"
|
||||
},
|
||||
"oauth_token": {
|
||||
"type": "string",
|
||||
"description": "OAuth 2.0 token for the current user.",
|
||||
"location": "query"
|
||||
},
|
||||
"prettyPrint": {
|
||||
"type": "boolean",
|
||||
"description": "Returns response with indentations and line breaks.",
|
||||
"default": "true",
|
||||
"location": "query"
|
||||
},
|
||||
"quotaUser": {
|
||||
"type": "string",
|
||||
"description": "Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters. Overrides userIp if both are provided.",
|
||||
"location": "query"
|
||||
},
|
||||
"userIp": {
|
||||
"type": "string",
|
||||
"description": "IP address of the site where the request originates. Use this if you want to enforce per-user limits.",
|
||||
"location": "query"
|
||||
}
|
||||
},
|
||||
"auth": {
|
||||
"oauth2": {
|
||||
"scopes": {
|
||||
"https://www.googleapis.com/auth/cloud-platform": {
|
||||
"description": "View and manage your data across Google Cloud Platform services"
|
||||
},
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only": {
|
||||
"description": "View your data across Google Cloud Platform services"
|
||||
},
|
||||
"https://www.googleapis.com/auth/ndev.cloudman": {
|
||||
"description": "View and manage your Google Cloud Platform management resources and deployment status information"
|
||||
},
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly": {
|
||||
"description": "View your Google Cloud Platform management resources and deployment status information"
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"schemas": {
|
||||
"Deployment": {
|
||||
"id": "Deployment",
|
||||
"type": "object",
|
||||
"description": "Next available tag: 8",
|
||||
"properties": {
|
||||
"description": {
|
||||
"type": "string",
|
||||
"description": "! An optional user-provided description of the deployment."
|
||||
},
|
||||
"id": {
|
||||
"type": "string",
|
||||
"description": "[Output Only] Unique identifier for the resource; defined by the server.",
|
||||
"format": "uint64"
|
||||
},
|
||||
"manifest": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] URL of the manifest representing the full configuration ! of this deployment."
|
||||
},
|
||||
"name": {
|
||||
"type": "string",
|
||||
"description": "! The name of the deployment, which must be unique within the project."
|
||||
},
|
||||
"targetConfig": {
|
||||
"type": "string",
|
||||
"description": "! [Input Only] The YAML configuration to use in processing this deployment. ! ! When you create a deployment, the server creates a new manifest with the ! given YAML configuration and sets the `manifest` property to the URL of ! the manifest resource."
|
||||
}
|
||||
}
|
||||
},
|
||||
"DeploymentsListResponse": {
|
||||
"id": "DeploymentsListResponse",
|
||||
"type": "object",
|
||||
"description": "! A response containing a partial list of deployments and a page token used ! to build the next request if the request has been truncated. Next available tag: 4",
|
||||
"properties": {
|
||||
"deployments": {
|
||||
"type": "array",
|
||||
"description": "! The deployments contained in this response.",
|
||||
"items": {
|
||||
"$ref": "Deployment"
|
||||
}
|
||||
},
|
||||
"nextPageToken": {
|
||||
"type": "string",
|
||||
"description": "! A token used to continue a truncated list request."
|
||||
}
|
||||
}
|
||||
},
|
||||
"Manifest": {
|
||||
"id": "Manifest",
|
||||
"type": "object",
|
||||
"description": "Next available tag: 10",
|
||||
"properties": {
|
||||
"config": {
|
||||
"type": "string",
|
||||
"description": "v2beta1: YAML with config - described above v2beta2: YAML + templates. ! The YAML configuration for this manifest."
|
||||
},
|
||||
"evaluatedConfig": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The fully-expanded configuration file, including any ! templates and references."
|
||||
},
|
||||
"id": {
|
||||
"type": "string",
|
||||
"description": "[Output Only] Unique identifier for the resource; defined by the server.",
|
||||
"format": "uint64"
|
||||
},
|
||||
"name": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The name of the manifest."
|
||||
},
|
||||
"selfLink": {
|
||||
"type": "string",
|
||||
"description": "[Output Only] Self link for the manifest."
|
||||
}
|
||||
}
|
||||
},
|
||||
"ManifestsListResponse": {
|
||||
"id": "ManifestsListResponse",
|
||||
"type": "object",
|
||||
"description": "! A response containing a partial list of manifests and a page token used ! to build the next request if the request has been truncated. Next available tag: 4",
|
||||
"properties": {
|
||||
"manifests": {
|
||||
"type": "array",
|
||||
"description": "! Manifests contained in this list response.",
|
||||
"items": {
|
||||
"$ref": "Manifest"
|
||||
}
|
||||
},
|
||||
"nextPageToken": {
|
||||
"type": "string",
|
||||
"description": "! A token used to continue a truncated list request."
|
||||
}
|
||||
}
|
||||
},
|
||||
"Operation": {
|
||||
"id": "Operation",
|
||||
"type": "object",
|
||||
"description": "! An operation resource, used to manage asynchronous API requests. Next available tag: 24",
|
||||
"properties": {
|
||||
"creationTimestamp": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] Creation timestamp in RFC3339 text format."
|
||||
},
|
||||
"endTime": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The time that this operation was completed. This is in ! RFC3339 format."
|
||||
},
|
||||
"error": {
|
||||
"type": "object",
|
||||
"description": "! [Output Only] If errors occurred during processing of this operation, ! this field will be populated.",
|
||||
"properties": {
|
||||
"errors": {
|
||||
"type": "array",
|
||||
"description": "! The array of errors encountered while processing this operation.",
|
||||
"items": {
|
||||
"type": "object",
|
||||
"properties": {
|
||||
"code": {
|
||||
"type": "string",
|
||||
"description": "! The error type identifier for this error."
|
||||
},
|
||||
"location": {
|
||||
"type": "string",
|
||||
"description": "! Indicates the field in the request which caused the error. ! This property is optional."
|
||||
},
|
||||
"message": {
|
||||
"type": "string",
|
||||
"description": "! An optional, human-readable error message."
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"httpErrorMessage": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] If operation fails, the HTTP error message returned, ! e.g. NOT FOUND."
|
||||
},
|
||||
"httpErrorStatusCode": {
|
||||
"type": "integer",
|
||||
"description": "! [Output Only] If operation fails, the HTTP error status code returned, ! e.g. 404.",
|
||||
"format": "int32"
|
||||
},
|
||||
"id": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] Unique identifier for the resource; defined by the server.",
|
||||
"format": "uint64"
|
||||
},
|
||||
"insertTime": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The time that this operation was requested. ! This is in RFC 3339 format."
|
||||
},
|
||||
"name": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] Name of the operation."
|
||||
},
|
||||
"operationType": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] Type of the operation. Examples include \"insert\", or ! \"delete\""
|
||||
},
|
||||
"progress": {
|
||||
"type": "integer",
|
||||
"description": "! [Output Only] An optional progress indicator that ranges from 0 to 100. ! There is no requirement that this be linear or support any granularity ! of operations. This should not be used to guess at when the operation will ! be complete. This number should be monotonically increasing as the ! operation progresses.",
|
||||
"format": "int32"
|
||||
},
|
||||
"selfLink": {
|
||||
"type": "string",
|
||||
"description": "[Output Only] Self link for the manifest."
|
||||
},
|
||||
"startTime": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The time that this operation was started by the server. ! This is in RFC 3339 format."
|
||||
},
|
||||
"status": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] Status of the operation. Can be one of the following: ! \"PENDING\", \"RUNNING\", or \"DONE\"."
|
||||
},
|
||||
"statusMessage": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] An optional textual description of the current status of ! the operation."
|
||||
},
|
||||
"targetId": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] Unique target id which identifies a particular ! incarnation of the target.",
|
||||
"format": "uint64"
|
||||
},
|
||||
"targetLink": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] URL of the resource the operation is mutating."
|
||||
},
|
||||
"user": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] User who requested the operation, for example ! \"user@example.com\""
|
||||
},
|
||||
"warnings": {
|
||||
"type": "array",
|
||||
"description": "! [Output Only] If warning messages generated during processing of this ! operation, this field will be populated.",
|
||||
"items": {
|
||||
"type": "object",
|
||||
"properties": {
|
||||
"code": {
|
||||
"type": "any",
|
||||
"description": "! The warning type identifier for this warning."
|
||||
},
|
||||
"data": {
|
||||
"type": "array",
|
||||
"description": "! Metadata for this warning in 'key: value' format.",
|
||||
"items": {
|
||||
"type": "object",
|
||||
"properties": {
|
||||
"key": {
|
||||
"type": "string",
|
||||
"description": "! A key for the warning data."
|
||||
},
|
||||
"value": {
|
||||
"type": "string",
|
||||
"description": "! A warning data value corresponding to the key."
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"message": {
|
||||
"type": "string",
|
||||
"description": "! Optional human-readable details for this warning."
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"OperationsListResponse": {
|
||||
"id": "OperationsListResponse",
|
||||
"type": "object",
|
||||
"description": "! A response containing a partial list of operations and a page token used ! to build the next request if the request has been truncated. Next available tag: 4",
|
||||
"properties": {
|
||||
"nextPageToken": {
|
||||
"type": "string",
|
||||
"description": "! A token used to continue a truncated list request."
|
||||
},
|
||||
"operations": {
|
||||
"type": "array",
|
||||
"description": "! Operations contained in this list response.",
|
||||
"items": {
|
||||
"$ref": "Operation"
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"Resource": {
|
||||
"id": "Resource",
|
||||
"type": "object",
|
||||
"description": "Next available tag: 12",
|
||||
"properties": {
|
||||
"errors": {
|
||||
"type": "array",
|
||||
"description": "! [Output Only] A list of any errors that occurred during deployment.",
|
||||
"items": {
|
||||
"type": "string"
|
||||
}
|
||||
},
|
||||
"id": {
|
||||
"type": "string",
|
||||
"description": "[Output Only] Unique identifier for the resource; defined by the server.",
|
||||
"format": "uint64"
|
||||
},
|
||||
"intent": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The intended state of the resource."
|
||||
},
|
||||
"manifest": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] URL of the manifest representing the current configuration ! of this resource."
|
||||
},
|
||||
"name": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The name of the resource as it appears in the YAML config."
|
||||
},
|
||||
"state": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The state of the resource."
|
||||
},
|
||||
"type": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The type of the resource, for example ! ?compute.v1.instance?, or ?replicaPools.v1beta2.instanceGroupManager?"
|
||||
},
|
||||
"url": {
|
||||
"type": "string",
|
||||
"description": "! [Output Only] The URL of the actual resource."
|
||||
}
|
||||
}
|
||||
},
|
||||
"ResourcesListResponse": {
|
||||
"id": "ResourcesListResponse",
|
||||
"type": "object",
|
||||
"description": "! A response containing a partial list of resources and a page token used ! to build the next request if the request has been truncated. Next available tag: 4",
|
||||
"properties": {
|
||||
"nextPageToken": {
|
||||
"type": "string",
|
||||
"description": "! A token used to continue a truncated list request."
|
||||
},
|
||||
"resources": {
|
||||
"type": "array",
|
||||
"description": "! Resources contained in this list response.",
|
||||
"items": {
|
||||
"$ref": "Resource"
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"Type": {
|
||||
"id": "Type",
|
||||
"type": "object",
|
||||
"description": "! A type supported by Deployment Manager. Next available tag: 4",
|
||||
"properties": {
|
||||
"name": {
|
||||
"type": "string",
|
||||
"description": "! Name of the type."
|
||||
}
|
||||
}
|
||||
},
|
||||
"TypesListResponse": {
|
||||
"id": "TypesListResponse",
|
||||
"type": "object",
|
||||
"description": "! A response that returns all Types supported by Deployment Manager Next available tag: 3",
|
||||
"properties": {
|
||||
"types": {
|
||||
"type": "array",
|
||||
"description": "! Types supported by Deployment Manager",
|
||||
"items": {
|
||||
"$ref": "Type"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
},
|
||||
"resources": {
|
||||
"deployments": {
|
||||
"methods": {
|
||||
"delete": {
|
||||
"id": "deploymentmanager.deployments.delete",
|
||||
"path": "{project}/global/deployments/{deployment}",
|
||||
"httpMethod": "DELETE",
|
||||
"description": "! Deletes a deployment and all of the resources in the deployment.",
|
||||
"parameters": {
|
||||
"deployment": {
|
||||
"type": "string",
|
||||
"description": "! The name of the deployment for this request.",
|
||||
"required": true,
|
||||
"pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
||||
"location": "path"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project",
|
||||
"deployment"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "Operation"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman"
|
||||
]
|
||||
},
|
||||
"get": {
|
||||
"id": "deploymentmanager.deployments.get",
|
||||
"path": "{project}/global/deployments/{deployment}",
|
||||
"httpMethod": "GET",
|
||||
"description": "! Gets information about a specific deployment.",
|
||||
"parameters": {
|
||||
"deployment": {
|
||||
"type": "string",
|
||||
"description": "! The name of the deployment for this request.",
|
||||
"required": true,
|
||||
"pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
||||
"location": "path"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project",
|
||||
"deployment"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "Deployment"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly"
|
||||
]
|
||||
},
|
||||
"insert": {
|
||||
"id": "deploymentmanager.deployments.insert",
|
||||
"path": "{project}/global/deployments",
|
||||
"httpMethod": "POST",
|
||||
"description": "! Creates a deployment and all of the resources described by the ! deployment manifest.",
|
||||
"parameters": {
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project"
|
||||
],
|
||||
"request": {
|
||||
"$ref": "Deployment"
|
||||
},
|
||||
"response": {
|
||||
"$ref": "Operation"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman"
|
||||
]
|
||||
},
|
||||
"list": {
|
||||
"id": "deploymentmanager.deployments.list",
|
||||
"path": "{project}/global/deployments",
|
||||
"httpMethod": "GET",
|
||||
"description": "! Lists all deployments for a given project.",
|
||||
"parameters": {
|
||||
"maxResults": {
|
||||
"type": "integer",
|
||||
"description": "! Maximum count of results to be returned. ! Acceptable values are 0 to 100, inclusive. (Default: 50)",
|
||||
"default": "50",
|
||||
"format": "int32",
|
||||
"minimum": "0",
|
||||
"maximum": "100",
|
||||
"location": "query"
|
||||
},
|
||||
"pageToken": {
|
||||
"type": "string",
|
||||
"description": "! Specifies a nextPageToken returned by a previous list request. This ! token can be used to request the next page of results from a previous ! list request.",
|
||||
"location": "query"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "DeploymentsListResponse"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly"
|
||||
]
|
||||
}
|
||||
}
|
||||
},
|
||||
"manifests": {
|
||||
"methods": {
|
||||
"get": {
|
||||
"id": "deploymentmanager.manifests.get",
|
||||
"path": "{project}/global/deployments/{deployment}/manifests/{manifest}",
|
||||
"httpMethod": "GET",
|
||||
"description": "! Gets information about a specific manifest.",
|
||||
"parameters": {
|
||||
"deployment": {
|
||||
"type": "string",
|
||||
"description": "! The name of the deployment for this request.",
|
||||
"required": true,
|
||||
"pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
||||
"location": "path"
|
||||
},
|
||||
"manifest": {
|
||||
"type": "string",
|
||||
"description": "! The name of the manifest for this request.",
|
||||
"required": true,
|
||||
"pattern": "[-a-z0-9]{1,61}",
|
||||
"location": "path"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project",
|
||||
"deployment",
|
||||
"manifest"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "Manifest"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly"
|
||||
]
|
||||
},
|
||||
"list": {
|
||||
"id": "deploymentmanager.manifests.list",
|
||||
"path": "{project}/global/deployments/{deployment}/manifests",
|
||||
"httpMethod": "GET",
|
||||
"description": "! Lists all manifests for a given deployment.",
|
||||
"parameters": {
|
||||
"deployment": {
|
||||
"type": "string",
|
||||
"description": "! The name of the deployment for this request.",
|
||||
"required": true,
|
||||
"pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
||||
"location": "path"
|
||||
},
|
||||
"maxResults": {
|
||||
"type": "integer",
|
||||
"description": "! Maximum count of results to be returned. ! Acceptable values are 0 to 100, inclusive. (Default: 50)",
|
||||
"default": "50",
|
||||
"format": "int32",
|
||||
"minimum": "0",
|
||||
"maximum": "100",
|
||||
"location": "query"
|
||||
},
|
||||
"pageToken": {
|
||||
"type": "string",
|
||||
"description": "! Specifies a nextPageToken returned by a previous list request. This ! token can be used to request the next page of results from a previous ! list request.",
|
||||
"location": "query"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project",
|
||||
"deployment"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "ManifestsListResponse"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly"
|
||||
]
|
||||
}
|
||||
}
|
||||
},
|
||||
"operations": {
|
||||
"methods": {
|
||||
"get": {
|
||||
"id": "deploymentmanager.operations.get",
|
||||
"path": "{project}/global/operations/{operation}",
|
||||
"httpMethod": "GET",
|
||||
"description": "! Gets information about a specific Operation.",
|
||||
"parameters": {
|
||||
"operation": {
|
||||
"type": "string",
|
||||
"description": "! The name of the operation for this request.",
|
||||
"required": true,
|
||||
"location": "path"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project",
|
||||
"operation"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "Operation"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly"
|
||||
]
|
||||
},
|
||||
"list": {
|
||||
"id": "deploymentmanager.operations.list",
|
||||
"path": "{project}/global/operations",
|
||||
"httpMethod": "GET",
|
||||
"description": "! Lists all Operations for a project.",
|
||||
"parameters": {
|
||||
"maxResults": {
|
||||
"type": "integer",
|
||||
"description": "! Maximum count of results to be returned. ! Acceptable values are 0 to 100, inclusive. (Default: 50)",
|
||||
"default": "50",
|
||||
"format": "int32",
|
||||
"minimum": "0",
|
||||
"maximum": "100",
|
||||
"location": "query"
|
||||
},
|
||||
"pageToken": {
|
||||
"type": "string",
|
||||
"description": "! Specifies a nextPageToken returned by a previous list request. This ! token can be used to request the next page of results from a previous ! list request.",
|
||||
"location": "query"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "OperationsListResponse"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly"
|
||||
]
|
||||
}
|
||||
}
|
||||
},
|
||||
"resources": {
|
||||
"methods": {
|
||||
"get": {
|
||||
"id": "deploymentmanager.resources.get",
|
||||
"path": "{project}/global/deployments/{deployment}/resources/{resource}",
|
||||
"httpMethod": "GET",
|
||||
"description": "! Gets information about a single resource.",
|
||||
"parameters": {
|
||||
"deployment": {
|
||||
"type": "string",
|
||||
"description": "! The name of the deployment for this request.",
|
||||
"required": true,
|
||||
"pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
||||
"location": "path"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
},
|
||||
"resource": {
|
||||
"type": "string",
|
||||
"description": "! The name of the resource for this request.",
|
||||
"required": true,
|
||||
"pattern": "[-a-z0-9]{1,61}",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project",
|
||||
"deployment",
|
||||
"resource"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "Resource"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly"
|
||||
]
|
||||
},
|
||||
"list": {
|
||||
"id": "deploymentmanager.resources.list",
|
||||
"path": "{project}/global/deployments/{deployment}/resources",
|
||||
"httpMethod": "GET",
|
||||
"description": "! Lists all resources in a given deployment.",
|
||||
"parameters": {
|
||||
"deployment": {
|
||||
"type": "string",
|
||||
"description": "! The name of the deployment for this request.",
|
||||
"required": true,
|
||||
"pattern": "[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?",
|
||||
"location": "path"
|
||||
},
|
||||
"maxResults": {
|
||||
"type": "integer",
|
||||
"description": "! Maximum count of results to be returned. ! Acceptable values are 0 to 100, inclusive. (Default: 50)",
|
||||
"default": "50",
|
||||
"format": "int32",
|
||||
"minimum": "0",
|
||||
"maximum": "100",
|
||||
"location": "query"
|
||||
},
|
||||
"pageToken": {
|
||||
"type": "string",
|
||||
"description": "! Specifies a nextPageToken returned by a previous list request. This ! token can be used to request the next page of results from a previous ! list request.",
|
||||
"location": "query"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project",
|
||||
"deployment"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "ResourcesListResponse"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly"
|
||||
]
|
||||
}
|
||||
}
|
||||
},
|
||||
"types": {
|
||||
"methods": {
|
||||
"list": {
|
||||
"id": "deploymentmanager.types.list",
|
||||
"path": "{project}/global/types",
|
||||
"httpMethod": "GET",
|
||||
"description": "! Lists all Types for Deployment Manager.",
|
||||
"parameters": {
|
||||
"maxResults": {
|
||||
"type": "integer",
|
||||
"description": "! Maximum count of results to be returned. ! Acceptable values are 0 to 100, inclusive. (Default: 50)",
|
||||
"default": "50",
|
||||
"format": "int32",
|
||||
"minimum": "0",
|
||||
"maximum": "100",
|
||||
"location": "query"
|
||||
},
|
||||
"pageToken": {
|
||||
"type": "string",
|
||||
"description": "! Specifies a nextPageToken returned by a previous list request. This ! token can be used to request the next page of results from a previous ! list request.",
|
||||
"location": "query"
|
||||
},
|
||||
"project": {
|
||||
"type": "string",
|
||||
"description": "! The project ID for this request.",
|
||||
"required": true,
|
||||
"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])?))",
|
||||
"location": "path"
|
||||
}
|
||||
},
|
||||
"parameterOrder": [
|
||||
"project"
|
||||
],
|
||||
"response": {
|
||||
"$ref": "TypesListResponse"
|
||||
},
|
||||
"scopes": [
|
||||
"https://www.googleapis.com/auth/cloud-platform",
|
||||
"https://www.googleapis.com/auth/cloud-platform.read-only",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman",
|
||||
"https://www.googleapis.com/auth/ndev.cloudman.readonly"
|
||||
]
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
2465
vendor/google.golang.org/api/deploymentmanager/v2beta1/deploymentmanager-gen.go
generated
vendored
2465
vendor/google.golang.org/api/deploymentmanager/v2beta1/deploymentmanager-gen.go
generated
vendored
File diff suppressed because it is too large
Load diff
1229
vendor/google.golang.org/api/deploymentmanager/v2beta2/deploymentmanager-api.json
generated
vendored
1229
vendor/google.golang.org/api/deploymentmanager/v2beta2/deploymentmanager-api.json
generated
vendored
File diff suppressed because it is too large
Load diff
3374
vendor/google.golang.org/api/deploymentmanager/v2beta2/deploymentmanager-gen.go
generated
vendored
3374
vendor/google.golang.org/api/deploymentmanager/v2beta2/deploymentmanager-gen.go
generated
vendored
File diff suppressed because it is too large
Load diff
Loading…
Add table
Add a link
Reference in a new issue