feat(servicemanagement): update the api

#### servicemanagement:v1

The following keys were deleted:
- schemas.EnableServiceResponse (Total Keys: 2)

Author: yoshi-automation

docs/dyn/servicemanagement_v1.services.rollouts.html

@@ -106,7 +106,7 @@ <h3>Method Details</h3>
 
 { # A rollout resource that defines how service configuration versions are pushed to control plane systems. Typically, you create a new version of the service config, and then create a Rollout to push the service config.
   &quot;createTime&quot;: &quot;A String&quot;, # Creation time of the rollout. Readonly.
-  &quot;createdBy&quot;: &quot;A String&quot;, # This field is deprecated and will be deleted. Please remove usage of this field.
+  &quot;createdBy&quot;: &quot;A String&quot;, # The user who created the Rollout. Readonly.
   &quot;deleteServiceStrategy&quot;: { # Strategy used to delete a service. This strategy is a placeholder only used by the system generated rollout to delete a service. # The strategy associated with a rollout to delete a `ManagedService`. Readonly.
   },
   &quot;rolloutId&quot;: &quot;A String&quot;, # Optional. Unique identifier of this Rollout. Must be no longer than 63 characters and only lower case letters, digits, &#x27;.&#x27;, &#x27;_&#x27; and &#x27;-&#x27; are allowed. If not specified by client, the server will generate one. The generated id will have the form of , where &quot;date&quot; is the create date in ISO 8601 format. &quot;revision number&quot; is a monotonically increasing positive number that is reset every day for each service. An example of the generated rollout_id is &#x27;2016-02-16r1&#x27;
@@ -165,7 +165,7 @@ <h3>Method Details</h3>
 
     { # A rollout resource that defines how service configuration versions are pushed to control plane systems. Typically, you create a new version of the service config, and then create a Rollout to push the service config.
   &quot;createTime&quot;: &quot;A String&quot;, # Creation time of the rollout. Readonly.
-  &quot;createdBy&quot;: &quot;A String&quot;, # This field is deprecated and will be deleted. Please remove usage of this field.
+  &quot;createdBy&quot;: &quot;A String&quot;, # The user who created the Rollout. Readonly.
   &quot;deleteServiceStrategy&quot;: { # Strategy used to delete a service. This strategy is a placeholder only used by the system generated rollout to delete a service. # The strategy associated with a rollout to delete a `ManagedService`. Readonly.
   },
   &quot;rolloutId&quot;: &quot;A String&quot;, # Optional. Unique identifier of this Rollout. Must be no longer than 63 characters and only lower case letters, digits, &#x27;.&#x27;, &#x27;_&#x27; and &#x27;-&#x27; are allowed. If not specified by client, the server will generate one. The generated id will have the form of , where &quot;date&quot; is the create date in ISO 8601 format. &quot;revision number&quot; is a monotonically increasing positive number that is reset every day for each service. An example of the generated rollout_id is &#x27;2016-02-16r1&#x27;
@@ -201,7 +201,7 @@ <h3>Method Details</h3>
   &quot;rollouts&quot;: [ # The list of rollout resources.
     { # A rollout resource that defines how service configuration versions are pushed to control plane systems. Typically, you create a new version of the service config, and then create a Rollout to push the service config.
       &quot;createTime&quot;: &quot;A String&quot;, # Creation time of the rollout. Readonly.
-      &quot;createdBy&quot;: &quot;A String&quot;, # This field is deprecated and will be deleted. Please remove usage of this field.
+      &quot;createdBy&quot;: &quot;A String&quot;, # The user who created the Rollout. Readonly.
       &quot;deleteServiceStrategy&quot;: { # Strategy used to delete a service. This strategy is a placeholder only used by the system generated rollout to delete a service. # The strategy associated with a rollout to delete a `ManagedService`. Readonly.
       },
       &quot;rolloutId&quot;: &quot;A String&quot;, # Optional. Unique identifier of this Rollout. Must be no longer than 63 characters and only lower case letters, digits, &#x27;.&#x27;, &#x27;_&#x27; and &#x27;-&#x27; are allowed. If not specified by client, the server will generate one. The generated id will have the form of , where &quot;date&quot; is the create date in ISO 8601 format. &quot;revision number&quot; is a monotonically increasing positive number that is reset every day for each service. An example of the generated rollout_id is &#x27;2016-02-16r1&#x27;

googleapiclient/discovery_cache/documents/servicemanagement.v1.json

@@ -829,7 +829,7 @@
       }
     }
   },
-  "revision": "20220204",
+  "revision": "20220218",
   "rootUrl": "https://servicemanagement.googleapis.com/",
   "schemas": {
     "Advice": {
@@ -1482,12 +1482,6 @@
       },
       "type": "object"
     },
-    "EnableServiceResponse": {
-      "description": "Operation payload for EnableService method.",
-      "id": "EnableServiceResponse",
-      "properties": {},
-      "type": "object"
-    },
     "Endpoint": {
       "description": "`Endpoint` describes a network address of a service that serves a set of APIs. It is commonly known as a service endpoint. A service may expose any number of service endpoints, and all service endpoints share the same service definition, such as quota limits and monitoring metrics. Example: type: google.api.Service name: library-example.googleapis.com endpoints: # Declares network address `https://library-example.googleapis.com` # for service `library-example.googleapis.com`. The `https` scheme # is implicit for all service endpoints. Other schemes may be # supported in the future. - name: library-example.googleapis.com allow_cors: false - name: content-staging-library-example.googleapis.com # Allows HTTP OPTIONS calls to be passed to the API frontend, for it # to decide whether the subsequent cross-origin request is allowed # to proceed. allow_cors: true",
       "id": "Endpoint",
@@ -2643,7 +2637,7 @@
           "type": "string"
         },
         "createdBy": {
-          "description": "This field is deprecated and will be deleted. Please remove usage of this field.",
+          "description": "The user who created the Rollout. Readonly.",
           "type": "string"
         },
         "deleteServiceStrategy": {