From 78d0ecaa9c0c2b9d37768a4fed1c5510e988e5aa Mon Sep 17 00:00:00 2001 From: Yoshi Automation Bot Date: Fri, 4 Oct 2024 13:16:46 +0000 Subject: [PATCH] feat: Automated regeneration of ServiceManagement client --- .../lib/google_api/service_management/v1/metadata.ex | 2 +- .../lib/google_api/service_management/v1/model/mixin.ex | 2 +- clients/service_management/mix.exs | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/clients/service_management/lib/google_api/service_management/v1/metadata.ex b/clients/service_management/lib/google_api/service_management/v1/metadata.ex index a748f5a462..2a0b108c75 100644 --- a/clients/service_management/lib/google_api/service_management/v1/metadata.ex +++ b/clients/service_management/lib/google_api/service_management/v1/metadata.ex @@ -20,7 +20,7 @@ defmodule GoogleApi.ServiceManagement.V1 do API client metadata for GoogleApi.ServiceManagement.V1. """ - @discovery_revision "20240920" + @discovery_revision "20240927" def discovery_revision(), do: @discovery_revision end diff --git a/clients/service_management/lib/google_api/service_management/v1/model/mixin.ex b/clients/service_management/lib/google_api/service_management/v1/model/mixin.ex index 3f0ade01a6..b28894e7d3 100644 --- a/clients/service_management/lib/google_api/service_management/v1/model/mixin.ex +++ b/clients/service_management/lib/google_api/service_management/v1/model/mixin.ex @@ -17,7 +17,7 @@ defmodule GoogleApi.ServiceManagement.V1.Model.Mixin do @moduledoc """ - Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = "/v1/{resource=**}:getAcl"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = "/v2/{resource=**}"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inherting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = "/v2/{resource=**}:getAcl"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = "/v2/acls/{resource=**}:getAcl"; } ... } + Declares an API Interface to be included in this interface. The including interface must redeclare all the methods from the included interface, but documentation and options are inherited as follows: - If after comment and whitespace stripping, the documentation string of the redeclared method is empty, it will be inherited from the original method. - Each annotation belonging to the service config (http, visibility) which is not set in the redeclared method will be inherited. - If an http annotation is inherited, the path pattern will be modified as follows. Any version prefix will be replaced by the version of the including interface plus the root path if specified. Example of a simple mixin: package google.acl.v1; service AccessControl { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = "/v1/{resource=**}:getAcl"; } } package google.storage.v2; service Storage { // rpc GetAcl(GetAclRequest) returns (Acl); // Get a data record. rpc GetData(GetDataRequest) returns (Data) { option (google.api.http).get = "/v2/{resource=**}"; } } Example of a mixin configuration: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl The mixin construct implies that all methods in `AccessControl` are also declared with same name and request/response types in `Storage`. A documentation generator or annotation processor will see the effective `Storage.GetAcl` method after inheriting documentation and annotations as follows: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = "/v2/{resource=**}:getAcl"; } ... } Note how the version in the path pattern changed from `v1` to `v2`. If the `root` field in the mixin is specified, it should be a relative path under which inherited HTTP paths are placed. Example: apis: - name: google.storage.v2.Storage mixins: - name: google.acl.v1.AccessControl root: acls This implies the following inherited HTTP annotation: service Storage { // Get the underlying ACL object. rpc GetAcl(GetAclRequest) returns (Acl) { option (google.api.http).get = "/v2/acls/{resource=**}:getAcl"; } ... } ## Attributes diff --git a/clients/service_management/mix.exs b/clients/service_management/mix.exs index a6ba282d66..cb3b5435d3 100644 --- a/clients/service_management/mix.exs +++ b/clients/service_management/mix.exs @@ -18,7 +18,7 @@ defmodule GoogleApi.ServiceManagement.Mixfile do use Mix.Project - @version "0.63.0" + @version "0.63.1" def project() do [