You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/backupdr_v1.projects.locations.backupPlans.html
+3-3
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ <h3>Method Details</h3>
107
107
body: object, The request body.
108
108
The object takes the form of:
109
109
110
-
{ # A `BackupPlan` specifies some common fields, such as `display_name` as well as one or more `BackupRule` messages. Each `BackupRule` has a retention policy and defines a schedule by which the system is to perform backup workloads.
110
+
{ # A `BackupPlan` specifies some common fields, such as `description` as well as one or more `BackupRule` messages. Each `BackupRule` has a retention policy and defines a schedule by which the system is to perform backup workloads.
111
111
"backupRules": [ # Required. The backup rules for this `BackupPlan`. There must be at least one `BackupRule` message.
112
112
{ # `BackupRule` binds the backup schedule to a retention policy.
113
113
"backupRetentionDays": 42, # Required. Configures the duration for which backup data will be kept. It is defined in “days”. The value should be greater than or equal to minimum enforced retention of the backup vault.
@@ -231,7 +231,7 @@ <h3>Method Details</h3>
231
231
Returns:
232
232
An object of the form:
233
233
234
-
{ # A `BackupPlan` specifies some common fields, such as `display_name` as well as one or more `BackupRule` messages. Each `BackupRule` has a retention policy and defines a schedule by which the system is to perform backup workloads.
234
+
{ # A `BackupPlan` specifies some common fields, such as `description` as well as one or more `BackupRule` messages. Each `BackupRule` has a retention policy and defines a schedule by which the system is to perform backup workloads.
235
235
"backupRules": [ # Required. The backup rules for this `BackupPlan`. There must be at least one `BackupRule` message.
236
236
{ # `BackupRule` binds the backup schedule to a retention policy.
237
237
"backupRetentionDays": 42, # Required. Configures the duration for which backup data will be kept. It is defined in “days”. The value should be greater than or equal to minimum enforced retention of the backup vault.
@@ -295,7 +295,7 @@ <h3>Method Details</h3>
295
295
296
296
{ # The response message for getting a list of `BackupPlan`.
297
297
"backupPlans": [ # The list of `BackupPlans` in the project for the specified location. If the `{location}` value in the request is "-", the response contains a list of resources from all locations. In case any location is unreachable, the response will only return backup plans in reachable locations and the 'unreachable' field will be populated with a list of unreachable locations. BackupPlan
298
-
{ # A `BackupPlan` specifies some common fields, such as `display_name` as well as one or more `BackupRule` messages. Each `BackupRule` has a retention policy and defines a schedule by which the system is to perform backup workloads.
298
+
{ # A `BackupPlan` specifies some common fields, such as `description` as well as one or more `BackupRule` messages. Each `BackupRule` has a retention policy and defines a schedule by which the system is to perform backup workloads.
299
299
"backupRules": [ # Required. The backup rules for this `BackupPlan`. There must be at least one `BackupRule` message.
300
300
{ # `BackupRule` binds the backup schedule to a retention policy.
301
301
"backupRetentionDays": 42, # Required. Configures the duration for which backup data will be kept. It is defined in “days”. The value should be greater than or equal to minimum enforced retention of the backup vault.
Copy file name to clipboardExpand all lines: docs/dyn/beyondcorp_v1alpha.projects.locations.global_.securityGateways.applications.html
+17-23
Original file line number
Diff line number
Diff line change
@@ -102,24 +102,21 @@ <h3>Method Details</h3>
102
102
The object takes the form of:
103
103
104
104
{ # A Beyondcorp Application resource information.
105
-
"applicationMatchFilter": { # Match Criteria for Application Filtering. # Required. Application filter conditions associated with an application.
106
-
"matchConditions": [ # Required. Match conditions for AND logic. An array of match conditions to allow for multiple matching criteria. The rule is considered a match if all the conditions are met. The conditions can be one of the following combination (FQDN), (FQDN & PORTS), (IP_ADDRESS), (IP_ADDRESS & PORTS) EXAMPLES: FQDN - ("*.abc.com"), ("xyz.abc.com") FQDN and PORTS - ("abc.com" and "22"), ("abc.com" and "22,33)" etc IP_ADDRESS - ("10.20.30.40"), ("100.20.30.40") IP_ADDRESS and PORTS - ("10.20.30.40" and "4"), ("10.20.30.40" and "4,5")
107
-
{ # Match condition for idenfying the application.
108
-
"fqdn": "A String", # Optional. FQDN of the application.
109
-
"ipAddress": "A String", # Optional. IP Address of the application.
110
-
"ports": [ # Optional. Ports of the application.
111
-
42,
112
-
],
113
-
},
114
-
],
115
-
},
116
105
"createTime": "A String", # Output only. Timestamp when the resource was created.
117
106
"displayName": "A String", # Optional. An arbitrary user-provided name for the Route resource. Cannot exceed 64 characters.
107
+
"endpointMatchers": [ # Required. Endpoint matchers associated with an application. A combination of hostname and ports as endpoint matcher is used to match the application. Match conditions for OR logic. An array of match conditions to allow for multiple matching criteria. The rule is considered a match if one the conditions are met. The conditions can be one of the following combination (Hostname), (Hostname & Ports) EXAMPLES: Hostname - ("*.abc.com"), ("xyz.abc.com") Hostname and Ports - ("abc.com" and "22"), ("abc.com" and "22,33") etc
108
+
{ # EndpointMatcher contains the information of the endpoint that will match the application.
109
+
"hostname": "A String", # Required. Hostname of the application.
110
+
"ports": [ # Optional. Ports of the application.
111
+
42,
112
+
],
113
+
},
114
+
],
118
115
"name": "A String", # Identifier. Name of the resource.
119
116
"updateTime": "A String", # Output only. Timestamp when the resource was last modified.
120
117
}
121
118
122
-
applicationId: string, Optional. User-settable Hub resource ID. * Must start with a letter. * Must contain between 4-63 characters from `/a-z-/`. * Must end with a number or letter.
119
+
applicationId: string, Optional. User-settable Application resource ID. * Must start with a letter. * Must contain between 4-63 characters from `/a-z-/`. * Must end with a number or letter.
123
120
requestId: string, Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request.
124
121
x__xgafv: string, V1 error format.
125
122
Allowed values
@@ -160,19 +157,16 @@ <h3>Method Details</h3>
160
157
The object takes the form of:
161
158
162
159
{ # A Beyondcorp Application resource information.
163
-
"applicationMatchFilter": { # Match Criteria for Application Filtering. # Required. Application filter conditions associated with an application.
164
-
"matchConditions": [ # Required. Match conditions for AND logic. An array of match conditions to allow for multiple matching criteria. The rule is considered a match if all the conditions are met. The conditions can be one of the following combination (FQDN), (FQDN & PORTS), (IP_ADDRESS), (IP_ADDRESS & PORTS) EXAMPLES: FQDN - ("*.abc.com"), ("xyz.abc.com") FQDN and PORTS - ("abc.com" and "22"), ("abc.com" and "22,33)" etc IP_ADDRESS - ("10.20.30.40"), ("100.20.30.40") IP_ADDRESS and PORTS - ("10.20.30.40" and "4"), ("10.20.30.40" and "4,5")
165
-
{ # Match condition for idenfying the application.
166
-
"fqdn": "A String", # Optional. FQDN of the application.
167
-
"ipAddress": "A String", # Optional. IP Address of the application.
168
-
"ports": [ # Optional. Ports of the application.
169
-
42,
170
-
],
171
-
},
172
-
],
173
-
},
174
160
"createTime": "A String", # Output only. Timestamp when the resource was created.
175
161
"displayName": "A String", # Optional. An arbitrary user-provided name for the Route resource. Cannot exceed 64 characters.
162
+
"endpointMatchers": [ # Required. Endpoint matchers associated with an application. A combination of hostname and ports as endpoint matcher is used to match the application. Match conditions for OR logic. An array of match conditions to allow for multiple matching criteria. The rule is considered a match if one the conditions are met. The conditions can be one of the following combination (Hostname), (Hostname & Ports) EXAMPLES: Hostname - ("*.abc.com"), ("xyz.abc.com") Hostname and Ports - ("abc.com" and "22"), ("abc.com" and "22,33") etc
163
+
{ # EndpointMatcher contains the information of the endpoint that will match the application.
164
+
"hostname": "A String", # Required. Hostname of the application.
165
+
"ports": [ # Optional. Ports of the application.
166
+
42,
167
+
],
168
+
},
169
+
],
176
170
"name": "A String", # Identifier. Name of the resource.
177
171
"updateTime": "A String", # Output only. Timestamp when the resource was last modified.
0 commit comments