feat(servicemanagement): update the api

#### servicemanagement:v1

The following keys were deleted:
- resources.services.methods.enable (Total Keys: 11)
- schemas.DisableServiceResponse (Total Keys: 2)
- schemas.EnableServiceRequest (Total Keys: 3)

Author: yoshi-automation

docs/dyn/servicemanagement_v1.services.html

@@ -98,9 +98,6 @@ <h2>Instance Methods</h2>
 <p class="toc_element">
   <code><a href="#delete">delete(serviceName, x__xgafv=None)</a></code></p>
 <p class="firstline">Deletes a managed service. This method will change the service to the `Soft-Delete` state for 30 days. Within this period, service producers may call UndeleteService to restore the service. After 30 days, the service will be permanently deleted. Operation</p>
-<p class="toc_element">
-  <code><a href="#enable">enable(serviceName, body=None, x__xgafv=None)</a></code></p>
-<p class="firstline">Enables a service for a project, so it can be used for the project. See [Cloud Auth Guide](https://cloud.google.com/docs/authentication) for more information. Operation</p>
 <p class="toc_element">
   <code><a href="#generateConfigReport">generateConfigReport(body=None, x__xgafv=None)</a></code></p>
 <p class="firstline">Generates and returns a report (errors, warnings and changes from existing configurations) associated with GenerateConfigReportRequest.new_value If GenerateConfigReportRequest.old_value is specified, GenerateConfigReportRequest will contain a single ChangeReport based on the comparison between GenerateConfigReportRequest.new_value and GenerateConfigReportRequest.old_value. If GenerateConfigReportRequest.old_value is not specified, this method will compare GenerateConfigReportRequest.new_value with the last pushed service configuration.</p>
@@ -211,48 +208,6 @@ <h3>Method Details</h3>
 }</pre>
 </div>
 
-<div class="method">
-    <code class="details" id="enable">enable(serviceName, body=None, x__xgafv=None)</code>
-  <pre>Enables a service for a project, so it can be used for the project. See [Cloud Auth Guide](https://cloud.google.com/docs/authentication) for more information. Operation
-
-Args:
-  serviceName: string, Required. Name of the service to enable. Specifying an unknown service name will cause the request to fail. (required)
-  body: object, The request body.
-    The object takes the form of:
-
-{ # Request message for EnableService method.
-  &quot;consumerId&quot;: &quot;A String&quot;, # Required. The identity of consumer resource which service enablement will be applied to. The Google Service Management implementation accepts the following forms: - &quot;project:&quot; Note: this is made compatible with google.api.servicecontrol.v1.Operation.consumer_id.
-}
-
-  x__xgafv: string, V1 error format.
-    Allowed values
-      1 - v1 error format
-      2 - v2 error format
-
-Returns:
-  An object of the form:
-
-    { # This resource represents a long-running operation that is the result of a network API call.
-  &quot;done&quot;: True or False, # If the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
-  &quot;error&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # The error result of the operation in case of failure or cancellation.
-    &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
-    &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
-      {
-        &quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
-      },
-    ],
-    &quot;message&quot;: &quot;A String&quot;, # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
-  },
-  &quot;metadata&quot;: { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
-    &quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
-  },
-  &quot;name&quot;: &quot;A String&quot;, # The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the `name` should be a resource name ending with `operations/{unique_id}`.
-  &quot;response&quot;: { # The normal response of the operation in case of success. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get`/`Create`/`Update`, the response should be the resource. For other methods, the response should have the type `XxxResponse`, where `Xxx` is the original method name. For example, if the original method name is `TakeSnapshot()`, the inferred response type is `TakeSnapshotResponse`.
-    &quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
-  },
-}</pre>
-</div>
-
 <div class="method">
     <code class="details" id="generateConfigReport">generateConfigReport(body=None, x__xgafv=None)</code>
   <pre>Generates and returns a report (errors, warnings and changes from existing configurations) associated with GenerateConfigReportRequest.new_value If GenerateConfigReportRequest.old_value is specified, GenerateConfigReportRequest will contain a single ChangeReport based on the comparison between GenerateConfigReportRequest.new_value and GenerateConfigReportRequest.old_value. If GenerateConfigReportRequest.old_value is not specified, this method will compare GenerateConfigReportRequest.new_value with the last pushed service configuration.

googleapiclient/discovery_cache/documents/servicemanagement.v1.json

@@ -228,34 +228,6 @@
                         "https://www.googleapis.com/auth/service.management"
                     ]
                 },
-                "enable": {
-                    "description": "Enables a service for a project, so it can be used for the project. See [Cloud Auth Guide](https://cloud.google.com/docs/authentication) for more information. Operation",
-                    "flatPath": "v1/services/{serviceName}:enable",
-                    "httpMethod": "POST",
-                    "id": "servicemanagement.services.enable",
-                    "parameterOrder": [
-                        "serviceName"
-                    ],
-                    "parameters": {
-                        "serviceName": {
-                            "description": "Required. Name of the service to enable. Specifying an unknown service name will cause the request to fail.",
-                            "location": "path",
-                            "required": true,
-                            "type": "string"
-                        }
-                    },
-                    "path": "v1/services/{serviceName}:enable",
-                    "request": {
-                        "$ref": "EnableServiceRequest"
-                    },
-                    "response": {
-                        "$ref": "Operation"
-                    },
-                    "scopes": [
-                        "https://www.googleapis.com/auth/cloud-platform",
-                        "https://www.googleapis.com/auth/service.management"
-                    ]
-                },
                 "generateConfigReport": {
                     "description": "Generates and returns a report (errors, warnings and changes from existing configurations) associated with GenerateConfigReportRequest.new_value If GenerateConfigReportRequest.old_value is specified, GenerateConfigReportRequest will contain a single ChangeReport based on the comparison between GenerateConfigReportRequest.new_value and GenerateConfigReportRequest.old_value. If GenerateConfigReportRequest.old_value is not specified, this method will compare GenerateConfigReportRequest.new_value with the last pushed service configuration.",
                     "flatPath": "v1/services:generateConfigReport",
@@ -857,7 +829,7 @@
             }
         }
     },
-    "revision": "20210219",
+    "revision": "20210319",
     "rootUrl": "https://servicemanagement.googleapis.com/",
     "schemas": {
         "Advice": {
@@ -1459,12 +1431,6 @@
             },
             "type": "object"
         },
-        "DisableServiceResponse": {
-            "description": "Operation payload for DisableService method.",
-            "id": "DisableServiceResponse",
-            "properties": {},
-            "type": "object"
-        },
         "Documentation": {
             "description": "`Documentation` provides the information for describing a service. Example: documentation: summary: > The Google Calendar API gives access to most calendar features. pages: - name: Overview content: (== include google/foo/overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==) subpages; - name: Java content: (== include google/foo/tutorial_java.md ==) rules: - selector: google.calendar.Calendar.Get description: > ... - selector: google.calendar.Calendar.Put description: > ... Documentation is provided in markdown syntax. In addition to standard markdown features, definition lists, tables and fenced code blocks are supported. Section headers can be provided and are interpreted relative to the section nesting of the context where a documentation fragment is embedded. Documentation from the IDL is merged with documentation defined via the config at normalization time, where documentation provided by config rules overrides IDL provided. A number of constructs specific to the API platform are supported in documentation text. In order to reference a proto element, the following notation can be used: [fully.qualified.proto.name][] To override the display text used for the link, this can be used: [display text][fully.qualified.proto.name] Text can be excluded from doc using the following notation: (-- internal comment --) A few directives are available in documentation. Note that directives must appear on a single line to be properly identified. The `include` directive includes a markdown file from an external source: (== include path/to/file ==) The `resource_for` directive marks a message to be the resource of a collection in REST view. If it is not specified, tools attempt to infer the resource from the operations in a collection: (== resource_for v1.shelves.books ==) The directive `suppress_warning` does not directly affect documentation and is documented together with service config validation.",
             "id": "Documentation",
@@ -1521,17 +1487,6 @@
             },
             "type": "object"
         },
-        "EnableServiceRequest": {
-            "description": "Request message for EnableService method.",
-            "id": "EnableServiceRequest",
-            "properties": {
-                "consumerId": {
-                    "description": "Required. The identity of consumer resource which service enablement will be applied to. The Google Service Management implementation accepts the following forms: - \"project:\" Note: this is made compatible with google.api.servicecontrol.v1.Operation.consumer_id.",
-                    "type": "string"
-                }
-            },
-            "type": "object"
-        },
         "EnableServiceResponse": {
             "description": "Operation payload for EnableService method.",
             "id": "EnableServiceResponse",