Skip to content

Commit 393dce7

Browse files
yoshi-automationyoshi-automation
committed
feat(memcache): update the api
#### memcache: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) #### memcache:v1beta2 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 bebdf70 commit 393dce7

File tree

2 files changed

+4
-82
lines changed

2 files changed

+4
-82
lines changed

‎googleapiclient/discovery_cache/documents/memcache.v1.json

Lines changed: 2 additions & 41 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
}
@@ -528,7 +528,7 @@
528528
}
529529
}
530530
},
531-
"revision": "20210823",
531+
"revision": "20210907",
532532
"rootUrl": "https://memcache.googleapis.com/",
533533
"schemas": {
534534
"ApplyParametersRequest": {
@@ -849,13 +849,6 @@
849849
"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.",
850850
"id": "GoogleCloudSaasacceleratorManagementProvidersV1NodeSloMetadata",
851851
"properties": {
852-
"exclusions": {
853-
"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.",
854-
"items": {
855-
"$ref": "GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion"
856-
},
857-
"type": "array"
858-
},
859852
"location": {
860853
"description": "The location of the node, if different from instance location.",
861854
"type": "string"
@@ -915,42 +908,10 @@
915908
},
916909
"type": "object"
917910
},
918-
"GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion": {
919-
"description": "SloExclusion represents an exclusion in SLI calculation applies to all SLOs.",
920-
"id": "GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion",
921-
"properties": {
922-
"duration": {
923-
"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.",
924-
"format": "google-duration",
925-
"type": "string"
926-
},
927-
"reason": {
928-
"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.",
929-
"type": "string"
930-
},
931-
"sliName": {
932-
"description": "Name of an SLI that this exclusion applies to. Can be left empty, signaling that the instance should be excluded from all SLIs.",
933-
"type": "string"
934-
},
935-
"startTime": {
936-
"description": "Start time of the exclusion. No alignment (e.g. to a full minute) needed.",
937-
"format": "google-datetime",
938-
"type": "string"
939-
}
940-
},
941-
"type": "object"
942-
},
943911
"GoogleCloudSaasacceleratorManagementProvidersV1SloMetadata": {
944912
"description": "SloMetadata contains resources required for proper SLO classification of the instance.",
945913
"id": "GoogleCloudSaasacceleratorManagementProvidersV1SloMetadata",
946914
"properties": {
947-
"exclusions": {
948-
"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.",
949-
"items": {
950-
"$ref": "GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion"
951-
},
952-
"type": "array"
953-
},
954915
"nodes": {
955916
"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.",
956917
"items": {

‎googleapiclient/discovery_cache/documents/memcache.v1beta2.json

Lines changed: 2 additions & 41 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
}
@@ -556,7 +556,7 @@
556556
}
557557
}
558558
},
559-
"revision": "20210823",
559+
"revision": "20210907",
560560
"rootUrl": "https://memcache.googleapis.com/",
561561
"schemas": {
562562
"ApplyParametersRequest": {
@@ -895,13 +895,6 @@
895895
"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.",
896896
"id": "GoogleCloudSaasacceleratorManagementProvidersV1NodeSloMetadata",
897897
"properties": {
898-
"exclusions": {
899-
"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.",
900-
"items": {
901-
"$ref": "GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion"
902-
},
903-
"type": "array"
904-
},
905898
"location": {
906899
"description": "The location of the node, if different from instance location.",
907900
"type": "string"
@@ -961,42 +954,10 @@
961954
},
962955
"type": "object"
963956
},
964-
"GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion": {
965-
"description": "SloExclusion represents an exclusion in SLI calculation applies to all SLOs.",
966-
"id": "GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion",
967-
"properties": {
968-
"duration": {
969-
"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.",
970-
"format": "google-duration",
971-
"type": "string"
972-
},
973-
"reason": {
974-
"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.",
975-
"type": "string"
976-
},
977-
"sliName": {
978-
"description": "Name of an SLI that this exclusion applies to. Can be left empty, signaling that the instance should be excluded from all SLIs.",
979-
"type": "string"
980-
},
981-
"startTime": {
982-
"description": "Start time of the exclusion. No alignment (e.g. to a full minute) needed.",
983-
"format": "google-datetime",
984-
"type": "string"
985-
}
986-
},
987-
"type": "object"
988-
},
989957
"GoogleCloudSaasacceleratorManagementProvidersV1SloMetadata": {
990958
"description": "SloMetadata contains resources required for proper SLO classification of the instance.",
991959
"id": "GoogleCloudSaasacceleratorManagementProvidersV1SloMetadata",
992960
"properties": {
993-
"exclusions": {
994-
"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.",
995-
"items": {
996-
"$ref": "GoogleCloudSaasacceleratorManagementProvidersV1SloExclusion"
997-
},
998-
"type": "array"
999-
},
1000961
"nodes": {
1001962
"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.",
1002963
"items": {

0 commit comments

Comments
 (0)