Skip to content

Commit

Permalink
feat(serviceconsumermanagement)!: update the API
Browse files Browse the repository at this point in the history
BREAKING CHANGE: This release has breaking changes.

#### serviceconsumermanagement:v1beta1

The following keys were deleted:
- schemas.Endpoint.properties.aliases.description
- schemas.Endpoint.properties.aliases.items.type
- schemas.Endpoint.properties.aliases.type

#### serviceconsumermanagement:v1

The following keys were deleted:
- schemas.Endpoint.properties.aliases.description
- schemas.Endpoint.properties.aliases.items.type
- schemas.Endpoint.properties.aliases.type
  • Loading branch information
yoshi-automation authored and sofisl committed Apr 20, 2021
1 parent 84de4b9 commit 429b8c1
Show file tree
Hide file tree
Showing 4 changed files with 2 additions and 24 deletions.
9 changes: 1 addition & 8 deletions discovery/serviceconsumermanagement-v1.json
Expand Up @@ -542,7 +542,7 @@
}
}
},
"revision": "20210331",
"revision": "20210413",
"rootUrl": "https://serviceconsumermanagement.googleapis.com/",
"schemas": {
"AddTenantProjectRequest": {
Expand Down Expand Up @@ -1063,13 +1063,6 @@
"description": "`Endpoint` describes a network endpoint 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 service configuration: name: library-example.googleapis.com endpoints: # Below entry makes 'google.example.library.v1.Library' # API be served from endpoint address library-example.googleapis.com. # It also allows HTTP OPTIONS calls to be passed to the backend, for # it to decide whether the subsequent cross-origin request is # allowed to proceed. - name: library-example.googleapis.com allow_cors: true",
"id": "Endpoint",
"properties": {
"aliases": {
"description": "DEPRECATED: This field is no longer supported. Instead of using aliases, please specify multiple google.api.Endpoint for each of the intended aliases. Additional names that this endpoint will be hosted on.",
"items": {
"type": "string"
},
"type": "array"
},
"allowCors": {
"description": "Allowing [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing), aka cross-domain traffic, would allow the backends served from this endpoint to receive and respond to HTTP OPTIONS requests. The response will be used by the browser to determine whether the subsequent cross-origin request is allowed to proceed.",
"type": "boolean"
Expand Down
9 changes: 1 addition & 8 deletions discovery/serviceconsumermanagement-v1beta1.json
Expand Up @@ -500,7 +500,7 @@
}
}
},
"revision": "20210331",
"revision": "20210413",
"rootUrl": "https://serviceconsumermanagement.googleapis.com/",
"schemas": {
"Api": {
Expand Down Expand Up @@ -933,13 +933,6 @@
"description": "`Endpoint` describes a network endpoint 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 service configuration: name: library-example.googleapis.com endpoints: # Below entry makes 'google.example.library.v1.Library' # API be served from endpoint address library-example.googleapis.com. # It also allows HTTP OPTIONS calls to be passed to the backend, for # it to decide whether the subsequent cross-origin request is # allowed to proceed. - name: library-example.googleapis.com allow_cors: true",
"id": "Endpoint",
"properties": {
"aliases": {
"description": "DEPRECATED: This field is no longer supported. Instead of using aliases, please specify multiple google.api.Endpoint for each of the intended aliases. Additional names that this endpoint will be hosted on.",
"items": {
"type": "string"
},
"type": "array"
},
"allowCors": {
"description": "Allowing [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing), aka cross-domain traffic, would allow the backends served from this endpoint to receive and respond to HTTP OPTIONS requests. The response will be used by the browser to determine whether the subsequent cross-origin request is allowed to proceed.",
"type": "boolean"
Expand Down
4 changes: 0 additions & 4 deletions src/apis/serviceconsumermanagement/v1.ts
Expand Up @@ -515,10 +515,6 @@ export namespace serviceconsumermanagement_v1 {
* `Endpoint` describes a network endpoint 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 service configuration: name: library-example.googleapis.com endpoints: # Below entry makes 'google.example.library.v1.Library' # API be served from endpoint address library-example.googleapis.com. # It also allows HTTP OPTIONS calls to be passed to the backend, for # it to decide whether the subsequent cross-origin request is # allowed to proceed. - name: library-example.googleapis.com allow_cors: true
*/
export interface Schema$Endpoint {
/**
* DEPRECATED: This field is no longer supported. Instead of using aliases, please specify multiple google.api.Endpoint for each of the intended aliases. Additional names that this endpoint will be hosted on.
*/
aliases?: string[] | null;
/**
* Allowing [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing), aka cross-domain traffic, would allow the backends served from this endpoint to receive and respond to HTTP OPTIONS requests. The response will be used by the browser to determine whether the subsequent cross-origin request is allowed to proceed.
*/
Expand Down
4 changes: 0 additions & 4 deletions src/apis/serviceconsumermanagement/v1beta1.ts
Expand Up @@ -441,10 +441,6 @@ export namespace serviceconsumermanagement_v1beta1 {
* `Endpoint` describes a network endpoint 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 service configuration: name: library-example.googleapis.com endpoints: # Below entry makes 'google.example.library.v1.Library' # API be served from endpoint address library-example.googleapis.com. # It also allows HTTP OPTIONS calls to be passed to the backend, for # it to decide whether the subsequent cross-origin request is # allowed to proceed. - name: library-example.googleapis.com allow_cors: true
*/
export interface Schema$Endpoint {
/**
* DEPRECATED: This field is no longer supported. Instead of using aliases, please specify multiple google.api.Endpoint for each of the intended aliases. Additional names that this endpoint will be hosted on.
*/
aliases?: string[] | null;
/**
* Allowing [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing), aka cross-domain traffic, would allow the backends served from this endpoint to receive and respond to HTTP OPTIONS requests. The response will be used by the browser to determine whether the subsequent cross-origin request is allowed to proceed.
*/
Expand Down

0 comments on commit 429b8c1

Please sign in to comment.