feat(serviceconsumermanagement): update the API

#### serviceconsumermanagement:v1beta1

The following keys were added:
- schemas.JwtLocation.properties.cookie.description
- schemas.JwtLocation.properties.cookie.type

The following keys were changed:
- schemas.AuthProvider.properties.jwtLocations.description

#### serviceconsumermanagement:v1

The following keys were added:
- schemas.JwtLocation.properties.cookie.description
- schemas.JwtLocation.properties.cookie.type

The following keys were changed:
- schemas.AuthProvider.properties.jwtLocations.description

discovery/serviceconsumermanagement-v1.json

@@ -542,7 +542,7 @@
       }
     }
   },
-  "revision": "20220321",
+  "revision": "20220406",
   "rootUrl": "https://serviceconsumermanagement.googleapis.com/",
   "schemas": {
     "AddTenantProjectRequest": {
@@ -671,7 +671,7 @@
           "type": "string"
         },
         "jwtLocations": {
-          "description": "Defines the locations to extract the JWT. JWT locations can be either from HTTP headers or URL query parameters. The rule is that the first match wins. The checking order is: checking all headers first, then URL query parameters. If not specified, default to use following 3 locations: 1) Authorization: Bearer 2) x-goog-iap-jwt-assertion 3) access_token query parameter Default locations can be specified as followings: jwt_locations: - header: Authorization value_prefix: \"Bearer \" - header: x-goog-iap-jwt-assertion - query: access_token",
+          "description": "Defines the locations to extract the JWT. For now it is only used by the Cloud Endpoints to store the OpenAPI extension [x-google-jwt-locations] (https://cloud.google.com/endpoints/docs/openapi/openapi-extensions#x-google-jwt-locations) JWT locations can be one of HTTP headers, URL query parameters or cookies. The rule is that the first match wins. If not specified, default to use following 3 locations: 1) Authorization: Bearer 2) x-goog-iap-jwt-assertion 3) access_token query parameter Default locations can be specified as followings: jwt_locations: - header: Authorization value_prefix: \"Bearer \" - header: x-goog-iap-jwt-assertion - query: access_token",
           "items": {
             "$ref": "JwtLocation"
           },
@@ -1315,6 +1315,10 @@
       "description": "Specifies a location to extract JWT from an API request.",
       "id": "JwtLocation",
       "properties": {
+        "cookie": {
+          "description": "Specifies cookie name to extract JWT token.",
+          "type": "string"
+        },
         "header": {
           "description": "Specifies HTTP header name to extract JWT token.",
           "type": "string"

discovery/serviceconsumermanagement-v1beta1.json

@@ -500,7 +500,7 @@
       }
     }
   },
-  "revision": "20220321",
+  "revision": "20220406",
   "rootUrl": "https://serviceconsumermanagement.googleapis.com/",
   "schemas": {
     "Api": {
@@ -580,7 +580,7 @@
           "type": "string"
         },
         "jwtLocations": {
-          "description": "Defines the locations to extract the JWT. JWT locations can be either from HTTP headers or URL query parameters. The rule is that the first match wins. The checking order is: checking all headers first, then URL query parameters. If not specified, default to use following 3 locations: 1) Authorization: Bearer 2) x-goog-iap-jwt-assertion 3) access_token query parameter Default locations can be specified as followings: jwt_locations: - header: Authorization value_prefix: \"Bearer \" - header: x-goog-iap-jwt-assertion - query: access_token",
+          "description": "Defines the locations to extract the JWT. For now it is only used by the Cloud Endpoints to store the OpenAPI extension [x-google-jwt-locations] (https://cloud.google.com/endpoints/docs/openapi/openapi-extensions#x-google-jwt-locations) JWT locations can be one of HTTP headers, URL query parameters or cookies. The rule is that the first match wins. If not specified, default to use following 3 locations: 1) Authorization: Bearer 2) x-goog-iap-jwt-assertion 3) access_token query parameter Default locations can be specified as followings: jwt_locations: - header: Authorization value_prefix: \"Bearer \" - header: x-goog-iap-jwt-assertion - query: access_token",
           "items": {
             "$ref": "JwtLocation"
           },
@@ -1185,6 +1185,10 @@
       "description": "Specifies a location to extract JWT from an API request.",
       "id": "JwtLocation",
       "properties": {
+        "cookie": {
+          "description": "Specifies cookie name to extract JWT token.",
+          "type": "string"
+        },
         "header": {
           "description": "Specifies HTTP header name to extract JWT token.",
           "type": "string"

src/apis/serviceconsumermanagement/v1.ts

@@ -262,7 +262,7 @@ export namespace serviceconsumermanagement_v1 {
      */
     jwksUri?: string | null;
     /**
-     * Defines the locations to extract the JWT. JWT locations can be either from HTTP headers or URL query parameters. The rule is that the first match wins. The checking order is: checking all headers first, then URL query parameters. If not specified, default to use following 3 locations: 1) Authorization: Bearer 2) x-goog-iap-jwt-assertion 3) access_token query parameter Default locations can be specified as followings: jwt_locations: - header: Authorization value_prefix: "Bearer " - header: x-goog-iap-jwt-assertion - query: access_token
+     * Defines the locations to extract the JWT. For now it is only used by the Cloud Endpoints to store the OpenAPI extension [x-google-jwt-locations] (https://cloud.google.com/endpoints/docs/openapi/openapi-extensions#x-google-jwt-locations) JWT locations can be one of HTTP headers, URL query parameters or cookies. The rule is that the first match wins. If not specified, default to use following 3 locations: 1) Authorization: Bearer 2) x-goog-iap-jwt-assertion 3) access_token query parameter Default locations can be specified as followings: jwt_locations: - header: Authorization value_prefix: "Bearer " - header: x-goog-iap-jwt-assertion - query: access_token
      */
     jwtLocations?: Schema$JwtLocation[];
   }
@@ -673,6 +673,10 @@ export namespace serviceconsumermanagement_v1 {
    * Specifies a location to extract JWT from an API request.
    */
   export interface Schema$JwtLocation {
+    /**
+     * Specifies cookie name to extract JWT token.
+     */
+    cookie?: string | null;
     /**
      * Specifies HTTP header name to extract JWT token.
      */

src/apis/serviceconsumermanagement/v1beta1.ts

@@ -219,7 +219,7 @@ export namespace serviceconsumermanagement_v1beta1 {
      */
     jwksUri?: string | null;
     /**
-     * Defines the locations to extract the JWT. JWT locations can be either from HTTP headers or URL query parameters. The rule is that the first match wins. The checking order is: checking all headers first, then URL query parameters. If not specified, default to use following 3 locations: 1) Authorization: Bearer 2) x-goog-iap-jwt-assertion 3) access_token query parameter Default locations can be specified as followings: jwt_locations: - header: Authorization value_prefix: "Bearer " - header: x-goog-iap-jwt-assertion - query: access_token
+     * Defines the locations to extract the JWT. For now it is only used by the Cloud Endpoints to store the OpenAPI extension [x-google-jwt-locations] (https://cloud.google.com/endpoints/docs/openapi/openapi-extensions#x-google-jwt-locations) JWT locations can be one of HTTP headers, URL query parameters or cookies. The rule is that the first match wins. If not specified, default to use following 3 locations: 1) Authorization: Bearer 2) x-goog-iap-jwt-assertion 3) access_token query parameter Default locations can be specified as followings: jwt_locations: - header: Authorization value_prefix: "Bearer " - header: x-goog-iap-jwt-assertion - query: access_token
      */
     jwtLocations?: Schema$JwtLocation[];
   }
@@ -599,6 +599,10 @@ export namespace serviceconsumermanagement_v1beta1 {
    * Specifies a location to extract JWT from an API request.
    */
   export interface Schema$JwtLocation {
+    /**
+     * Specifies cookie name to extract JWT token.
+     */
+    cookie?: string | null;
     /**
      * Specifies HTTP header name to extract JWT token.
      */