Skip to content

Commit 9f85c13

Browse files
feat(managedidentities): update the api
#### managedidentities:v1 The following keys were deleted: - schemas.GoogleCloudSaasacceleratorManagementProvidersV1NodeSloMetadata.properties.exclusions (Total Keys: 2) - schemas.GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion (Total Keys: 8) - schemas.GoogleCloudSaasacceleratorManagementProvidersV1SloMetadata.properties.exclusions (Total Keys: 2) The following keys were added: - resources.projects.resources.locations.resources.global.resources.peerings.methods.getIamPolicy (Total Keys: 14) - resources.projects.resources.locations.resources.global.resources.peerings.methods.setIamPolicy (Total Keys: 12) - resources.projects.resources.locations.resources.global.resources.peerings.methods.testIamPermissions (Total Keys: 12) #### managedidentities:v1alpha1 The following keys were deleted: - schemas.GoogleCloudSaasacceleratorManagementProvidersV1NodeSloMetadata.properties.exclusions (Total Keys: 2) - schemas.GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion (Total Keys: 8) - schemas.GoogleCloudSaasacceleratorManagementProvidersV1SloMetadata.properties.exclusions (Total Keys: 2) #### managedidentities:v1beta1 The following keys were deleted: - schemas.GoogleCloudSaasacceleratorManagementProvidersV1NodeSloMetadata.properties.exclusions (Total Keys: 2) - schemas.GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion (Total Keys: 8) - schemas.GoogleCloudSaasacceleratorManagementProvidersV1SloMetadata.properties.exclusions (Total Keys: 2)
1 parent 55ba494 commit 9f85c13

12 files changed

+352
-155
lines changed

docs/dyn/managedidentities_v1.projects.locations.global_.domains.html

Lines changed: 4 additions & 4 deletions
Large diffs are not rendered by default.

docs/dyn/managedidentities_v1.projects.locations.global_.html

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,11 @@ <h2>Instance Methods</h2>
8484
</p>
8585
<p class="firstline">Returns the operations Resource.</p>
8686

87+
<p class="toc_element">
88+
<code><a href="managedidentities_v1.projects.locations.global_.peerings.html">peerings()</a></code>
89+
</p>
90+
<p class="firstline">Returns the peerings Resource.</p>
91+
8792
<p class="toc_element">
8893
<code><a href="#close">close()</a></code></p>
8994
<p class="firstline">Close httplib2 connections.</p>

docs/dyn/managedidentities_v1.projects.locations.global_.peerings.html

Lines changed: 218 additions & 0 deletions
Large diffs are not rendered by default.

docs/dyn/managedidentities_v1alpha1.projects.locations.global_.domains.backups.html

Lines changed: 3 additions & 3 deletions
Large diffs are not rendered by default.

docs/dyn/managedidentities_v1alpha1.projects.locations.global_.domains.html

Lines changed: 3 additions & 3 deletions
Large diffs are not rendered by default.

docs/dyn/managedidentities_v1alpha1.projects.locations.global_.peerings.html

Lines changed: 3 additions & 3 deletions
Large diffs are not rendered by default.

docs/dyn/managedidentities_v1beta1.projects.locations.global_.domains.backups.html

Lines changed: 3 additions & 3 deletions
Large diffs are not rendered by default.

docs/dyn/managedidentities_v1beta1.projects.locations.global_.domains.html

Lines changed: 3 additions & 3 deletions
Large diffs are not rendered by default.

docs/dyn/managedidentities_v1beta1.projects.locations.global_.peerings.html

Lines changed: 3 additions & 3 deletions
Large diffs are not rendered by default.

googleapiclient/discovery_cache/documents/managedidentities.v1.json

Lines changed: 97 additions & 45 deletions
Large diffs are not rendered by default.

googleapiclient/discovery_cache/documents/managedidentities.v1alpha1.json

Lines changed: 5 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
"oauth2": {
44
"scopes": {
55
"https://www.googleapis.com/auth/cloud-platform": {
6-
"description": "See, edit, configure, and delete your Google Cloud Platform data"
6+
"description": "See, edit, configure, and delete your Google Cloud data and see the email address for your Google Account."
77
}
88
}
99
}
@@ -1184,7 +1184,7 @@
11841184
}
11851185
}
11861186
},
1187-
"revision": "20210701",
1187+
"revision": "20210819",
11881188
"rootUrl": "https://managedidentities.googleapis.com/",
11891189
"schemas": {
11901190
"AttachTrustRequest": {
@@ -1729,13 +1729,6 @@
17291729
"description": "Node information for custom per-node SLO implementations. SSA does not support per-node SLO, but producers can populate per-node information in SloMetadata for custom precomputations. SSA Eligibility Exporter will emit per-node metric based on this information.",
17301730
"id": "GoogleCloudSaasacceleratorManagementProvidersV1NodeSloMetadata",
17311731
"properties": {
1732-
"exclusions": {
1733-
"description": "By default node is eligible if instance is eligible. But individual node might be excluded from SLO by adding entry here. For semantic see SloMetadata.exclusions. If both instance and node level exclusions are present for time period, the node level's reason will be reported by Eligibility Exporter.",
1734-
"items": {
1735-
"$ref": "GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion"
1736-
},
1737-
"type": "array"
1738-
},
17391732
"location": {
17401733
"description": "The location of the node, if different from instance location.",
17411734
"type": "string"
@@ -1795,42 +1788,10 @@
17951788
},
17961789
"type": "object"
17971790
},
1798-
"GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion": {
1799-
"description": "SloExclusion represents an exclusion in SLI calculation applies to all SLOs.",
1800-
"id": "GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion",
1801-
"properties": {
1802-
"duration": {
1803-
"description": "Exclusion duration. No restrictions on the possible values. When an ongoing operation is taking longer than initially expected, an existing entry in the exclusion list can be updated by extending the duration. This is supported by the subsystem exporting eligibility data as long as such extension is committed at least 10 minutes before the original exclusion expiration - otherwise it is possible that there will be \"gaps\" in the exclusion application in the exported timeseries.",
1804-
"format": "google-duration",
1805-
"type": "string"
1806-
},
1807-
"reason": {
1808-
"description": "Human-readable reason for the exclusion. This should be a static string (e.g. \"Disruptive update in progress\") and should not contain dynamically generated data (e.g. instance name). Can be left empty.",
1809-
"type": "string"
1810-
},
1811-
"sliName": {
1812-
"description": "Name of an SLI that this exclusion applies to. Can be left empty, signaling that the instance should be excluded from all SLIs.",
1813-
"type": "string"
1814-
},
1815-
"startTime": {
1816-
"description": "Start time of the exclusion. No alignment (e.g. to a full minute) needed.",
1817-
"format": "google-datetime",
1818-
"type": "string"
1819-
}
1820-
},
1821-
"type": "object"
1822-
},
18231791
"GoogleCloudSaasacceleratorManagementProvidersV1SloMetadata": {
18241792
"description": "SloMetadata contains resources required for proper SLO classification of the instance.",
18251793
"id": "GoogleCloudSaasacceleratorManagementProvidersV1SloMetadata",
18261794
"properties": {
1827-
"exclusions": {
1828-
"description": "List of SLO exclusion windows. When multiple entries in the list match (matching the exclusion time-window against current time point) the exclusion reason used in the first matching entry will be published. It is not needed to include expired exclusion in this list, as only the currently applicable exclusions are taken into account by the eligibility exporting subsystem (the historical state of exclusions will be reflected in the historically produced timeseries regardless of the current state). This field can be used to mark the instance as temporary ineligible for the purpose of SLO calculation. For permanent instance SLO exclusion, use of custom instance eligibility is recommended. See 'eligibility' field below.",
1829-
"items": {
1830-
"$ref": "GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion"
1831-
},
1832-
"type": "array"
1833-
},
18341795
"nodes": {
18351796
"description": "Optional. List of nodes. Some producers need to use per-node metadata to calculate SLO. This field allows such producers to publish per-node SLO meta data, which will be consumed by SSA Eligibility Exporter and published in the form of per node metric to Monarch.",
18361797
"items": {
@@ -2151,7 +2112,7 @@
21512112
"type": "string"
21522113
},
21532114
"cancelRequested": {
2154-
"description": "Output only. Identifies whether the user has requested cancellation of the operation. Operations that have successfully been cancelled have Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
2115+
"description": "Output only. Identifies whether the user has requested cancellation of the operation. Operations that have been cancelled successfully have Operation.error value with a google.rpc.Status.code of 1, corresponding to `Code.CANCELLED`.",
21552116
"readOnly": true,
21562117
"type": "boolean"
21572118
},
@@ -2249,7 +2210,7 @@
22492210
"type": "object"
22502211
},
22512212
"Policy": {
2252-
"description": "An Identity and Access Management (IAM) policy, which specifies access controls for Google Cloud resources. A `Policy` is a collection of `bindings`. A `binding` binds one or more `members` to a single `role`. Members can be user accounts, service accounts, Google groups, and domains (such as G Suite). A `role` is a named list of permissions; each `role` can be an IAM predefined role or a user-created custom role. For some types of Google Cloud resources, a `binding` can also specify a `condition`, which is a logical expression that allows access to a resource only if the expression evaluates to `true`. A condition can add constraints based on attributes of the request, the resource, or both. To learn which resources support conditions in their IAM policies, see the [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies). **JSON example:** { \"bindings\": [ { \"role\": \"roles/resourcemanager.organizationAdmin\", \"members\": [ \"user:[email protected]\", \"group:[email protected]\", \"domain:google.com\", \"serviceAccount:[email protected]\" ] }, { \"role\": \"roles/resourcemanager.organizationViewer\", \"members\": [ \"user:[email protected]\" ], \"condition\": { \"title\": \"expirable access\", \"description\": \"Does not grant access after Sep 2020\", \"expression\": \"request.time < timestamp('2020-10-01T00:00:00.000Z')\", } } ], \"etag\": \"BwWWja0YfJA=\", \"version\": 3 } **YAML example:** bindings: - members: - user:[email protected] - group:[email protected] - domain:google.com - serviceAccount:[email protected] role: roles/resourcemanager.organizationAdmin - members: - user:[email protected] role: roles/resourcemanager.organizationViewer condition: title: expirable access description: Does not grant access after Sep 2020 expression: request.time < timestamp('2020-10-01T00:00:00.000Z') - etag: BwWWja0YfJA= - version: 3 For a description of IAM and its features, see the [IAM documentation](https://cloud.google.com/iam/docs/).",
2213+
"description": "An Identity and Access Management (IAM) policy, which specifies access controls for Google Cloud resources. A `Policy` is a collection of `bindings`. A `binding` binds one or more `members` to a single `role`. Members can be user accounts, service accounts, Google groups, and domains (such as G Suite). A `role` is a named list of permissions; each `role` can be an IAM predefined role or a user-created custom role. For some types of Google Cloud resources, a `binding` can also specify a `condition`, which is a logical expression that allows access to a resource only if the expression evaluates to `true`. A condition can add constraints based on attributes of the request, the resource, or both. To learn which resources support conditions in their IAM policies, see the [IAM documentation](https://cloud.google.com/iam/help/conditions/resource-policies). **JSON example:** { \"bindings\": [ { \"role\": \"roles/resourcemanager.organizationAdmin\", \"members\": [ \"user:[email protected]\", \"group:[email protected]\", \"domain:google.com\", \"serviceAccount:[email protected]\" ] }, { \"role\": \"roles/resourcemanager.organizationViewer\", \"members\": [ \"user:[email protected]\" ], \"condition\": { \"title\": \"expirable access\", \"description\": \"Does not grant access after Sep 2020\", \"expression\": \"request.time < timestamp('2020-10-01T00:00:00.000Z')\", } } ], \"etag\": \"BwWWja0YfJA=\", \"version\": 3 } **YAML example:** bindings: - members: - user:[email protected] - group:[email protected] - domain:google.com - serviceAccount:[email protected] role: roles/resourcemanager.organizationAdmin - members: - user:[email protected] role: roles/resourcemanager.organizationViewer condition: title: expirable access description: Does not grant access after Sep 2020 expression: request.time < timestamp('2020-10-01T00:00:00.000Z') etag: BwWWja0YfJA= version: 3 For a description of IAM and its features, see the [IAM documentation](https://cloud.google.com/iam/docs/).",
22532214
"id": "Policy",
22542215
"properties": {
22552216
"bindings": {
@@ -2588,7 +2549,7 @@
25882549
"type": "string"
25892550
},
25902551
"denyMaintenancePeriods": {
2591-
"description": "Deny Maintenance Period that is applied to resource to indicate when maintenance is forbidden. User can specify zero or more non-overlapping deny periods. For V1, Maximum number of deny_maintenance_periods is expected to be one.",
2552+
"description": "Deny Maintenance Period that is applied to resource to indicate when maintenance is forbidden. User can specify zero or more non-overlapping deny periods. Maximum number of deny_maintenance_periods expected is one.",
25922553
"items": {
25932554
"$ref": "DenyMaintenancePeriod"
25942555
},

0 commit comments

Comments
 (0)