feat(appengine): update the api

#### appengine:v1 The following keys were deleted: - schemas.ContainerState.properties.currentReasons.deprecated (Total Keys: 1) - schemas.ContainerState.properties.previousReasons.deprecated (Total Keys: 1) The following keys were added: - schemas.Runtime.properties.displayName.type (Total Keys: 1) #### appengine:v1alpha The following keys were deleted: - schemas.ContainerState.properties.currentReasons.deprecated (Total Keys: 1) - schemas.ContainerState.properties.previousReasons.deprecated (Total Keys: 1) #### appengine:v1beta The following keys were deleted: - schemas.ContainerState.properties.currentReasons.deprecated (Total Keys: 1) - schemas.ContainerState.properties.previousReasons.deprecated (Total Keys: 1) The following keys were added: - schemas.Runtime.properties.displayName.type (Total Keys: 1)
googleapis · Feb 27, 2024 · 16d304f · 16d304f
1 parent b7ae824
commit 16d304f
Show file tree

Hide file tree

Showing 5 changed files with 19 additions and 15 deletions.
diff --git a/docs/dyn/appengine_v1.apps.html b/docs/dyn/appengine_v1.apps.html
@@ -293,6 +293,7 @@ <h3>Method Details</h3>
         &quot;month&quot;: 42, # Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
         &quot;year&quot;: 42, # Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
       },
+      &quot;displayName&quot;: &quot;A String&quot;, # User-friendly display name, e.g. &#x27;Node.js 12&#x27;, etc.
       &quot;endOfSupportDate&quot;: { # Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: A full date, with non-zero year, month, and day values. A month and day, with a zero year (for example, an anniversary). A year on its own, with a zero month and a zero day. A year and month, with a zero day (for example, a credit card expiration date).Related types: google.type.TimeOfDay google.type.DateTime google.protobuf.Timestamp # Date when Runtime is end of support.
         &quot;day&quot;: 42, # Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn&#x27;t significant.
         &quot;month&quot;: 42, # Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

diff --git a/docs/dyn/appengine_v1beta.apps.html b/docs/dyn/appengine_v1beta.apps.html
@@ -293,6 +293,7 @@ <h3>Method Details</h3>
         &quot;month&quot;: 42, # Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.
         &quot;year&quot;: 42, # Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.
       },
+      &quot;displayName&quot;: &quot;A String&quot;, # User-friendly display name, e.g. &#x27;Node.js 12&#x27;, etc.
       &quot;endOfSupportDate&quot;: { # Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: A full date, with non-zero year, month, and day values. A month and day, with a zero year (for example, an anniversary). A year on its own, with a zero month and a zero day. A year and month, with a zero day (for example, a credit card expiration date).Related types: google.type.TimeOfDay google.type.DateTime google.protobuf.Timestamp # Date when Runtime is end of support.
         &quot;day&quot;: 42, # Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn&#x27;t significant.
         &quot;month&quot;: 42, # Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

diff --git a/googleapiclient/discovery_cache/documents/appengine.v1.json b/googleapiclient/discovery_cache/documents/appengine.v1.json
@@ -1651,7 +1651,7 @@
 }
 }
 },
-"revision": "20240212",
+"revision": "20240218",
 "rootUrl": "https://appengine.googleapis.com/",
 "schemas": {
 "ApiConfigHandler": {
@@ -2060,13 +2060,11 @@
 "id": "ContainerState",
 "properties": {
 "currentReasons": {
-"$ref": "Reasons",
-"deprecated": true
+"$ref": "Reasons"
 },
 "previousReasons": {
 "$ref": "Reasons",
-"deprecated": true,
-"description": "The previous and current reasons for a container state will be sent for a container event. CLHs that need to know the signal that caused the container event to trigger (edges) as opposed to just knowing the state can act upon differences in the previous and current reasons.Reasons will be provided for every system: service management, data governance, abuse, and billing.If this is a CCFE-triggered event used for reconciliation then the current reasons will be set to their *_CONTROL_PLANE_SYNC state. The previous reasons will contain the last known set of non-unknown non-control_plane_sync reasons for the state.Reasons fields are deprecated. New tenants should only use the state field. If you must know the reason(s) behind a specific state, please consult with CCFE team first (cloud-ccfe-discuss@google.com)."
+"description": "The previous and current reasons for a container state will be sent for a container event. CLHs that need to know the signal that caused the container event to trigger (edges) as opposed to just knowing the state can act upon differences in the previous and current reasons.Reasons will be provided for every system: service management, data governance, abuse, and billing.If this is a CCFE-triggered event used for reconciliation then the current reasons will be set to their *_CONTROL_PLANE_SYNC state. The previous reasons will contain the last known set of non-unknown non-control_plane_sync reasons for the state."
 },
 "state": {
 "description": "The current state of the container. This state is the culmination of all of the opinions from external systems that CCFE knows about of the container.",
@@ -3524,6 +3522,10 @@ true
 "$ref": "Date",
 "description": "Date when Runtime is deprecated."
 },
+"displayName": {
+"description": "User-friendly display name, e.g. 'Node.js 12', etc.",
+"type": "string"
+},
 "endOfSupportDate": {
 "$ref": "Date",
 "description": "Date when Runtime is end of support."

diff --git a/googleapiclient/discovery_cache/documents/appengine.v1alpha.json b/googleapiclient/discovery_cache/documents/appengine.v1alpha.json
@@ -887,7 +887,7 @@
 }
 }
 },
-"revision": "20240212",
+"revision": "20240218",
 "rootUrl": "https://appengine.googleapis.com/",
 "schemas": {
 "AuthorizedCertificate": {
@@ -976,13 +976,11 @@
 "id": "ContainerState",
 "properties": {
 "currentReasons": {
-"$ref": "Reasons",
-"deprecated": true
+"$ref": "Reasons"
 },
 "previousReasons": {
 "$ref": "Reasons",
-"deprecated": true,
-"description": "The previous and current reasons for a container state will be sent for a container event. CLHs that need to know the signal that caused the container event to trigger (edges) as opposed to just knowing the state can act upon differences in the previous and current reasons.Reasons will be provided for every system: service management, data governance, abuse, and billing.If this is a CCFE-triggered event used for reconciliation then the current reasons will be set to their *_CONTROL_PLANE_SYNC state. The previous reasons will contain the last known set of non-unknown non-control_plane_sync reasons for the state.Reasons fields are deprecated. New tenants should only use the state field. If you must know the reason(s) behind a specific state, please consult with CCFE team first (cloud-ccfe-discuss@google.com)."
+"description": "The previous and current reasons for a container state will be sent for a container event. CLHs that need to know the signal that caused the container event to trigger (edges) as opposed to just knowing the state can act upon differences in the previous and current reasons.Reasons will be provided for every system: service management, data governance, abuse, and billing.If this is a CCFE-triggered event used for reconciliation then the current reasons will be set to their *_CONTROL_PLANE_SYNC state. The previous reasons will contain the last known set of non-unknown non-control_plane_sync reasons for the state."
 },
 "state": {
 "description": "The current state of the container. This state is the culmination of all of the opinions from external systems that CCFE knows about of the container.",

diff --git a/googleapiclient/discovery_cache/documents/appengine.v1beta.json b/googleapiclient/discovery_cache/documents/appengine.v1beta.json
@@ -1859,7 +1859,7 @@
 }
 }
 },
-"revision": "20240212",
+"revision": "20240218",
 "rootUrl": "https://appengine.googleapis.com/",
 "schemas": {
 "ApiConfigHandler": {
@@ -2286,13 +2286,11 @@
 "id": "ContainerState",
 "properties": {
 "currentReasons": {
-"$ref": "Reasons",
-"deprecated": true
+"$ref": "Reasons"
 },
 "previousReasons": {
 "$ref": "Reasons",
-"deprecated": true,
-"description": "The previous and current reasons for a container state will be sent for a container event. CLHs that need to know the signal that caused the container event to trigger (edges) as opposed to just knowing the state can act upon differences in the previous and current reasons.Reasons will be provided for every system: service management, data governance, abuse, and billing.If this is a CCFE-triggered event used for reconciliation then the current reasons will be set to their *_CONTROL_PLANE_SYNC state. The previous reasons will contain the last known set of non-unknown non-control_plane_sync reasons for the state.Reasons fields are deprecated. New tenants should only use the state field. If you must know the reason(s) behind a specific state, please consult with CCFE team first (cloud-ccfe-discuss@google.com)."
+"description": "The previous and current reasons for a container state will be sent for a container event. CLHs that need to know the signal that caused the container event to trigger (edges) as opposed to just knowing the state can act upon differences in the previous and current reasons.Reasons will be provided for every system: service management, data governance, abuse, and billing.If this is a CCFE-triggered event used for reconciliation then the current reasons will be set to their *_CONTROL_PLANE_SYNC state. The previous reasons will contain the last known set of non-unknown non-control_plane_sync reasons for the state."
 },
 "state": {
 "description": "The current state of the container. This state is the culmination of all of the opinions from external systems that CCFE knows about of the container.",
@@ -3781,6 +3779,10 @@ true
 "$ref": "Date",
 "description": "Date when Runtime is deprecated."
 },
+"displayName": {
+"description": "User-friendly display name, e.g. 'Node.js 12', etc.",
+"type": "string"
+},
 "endOfSupportDate": {
 "$ref": "Date",
 "description": "Date when Runtime is end of support."