-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated clients are missing routing headers #401
Comments
Just to clarify, is this an issue being seen with microgenerated client libraries? |
Hi, is there any update on this bug? We need to get the python snippets in before our GA launch, as this is currently one of our blockers. |
Bumping the priority on this as I'm seeing the same issue with KMS. Errors look like: EDIT: Looks like this is slightly different (perhaps related to pagination?). I don't see the error with my test project which has fewer resources.
|
The original issue with service_directory seems to be that the generator currently adds the metadata only for // Creates a namespace, and returns the new Namespace.
rpc CreateNamespace(CreateNamespaceRequest) returns (Namespace) {
option (google.api.http) = {
post: "/v1beta1/{parent=projects/*/locations/*}/namespaces"
body: "namespace"
};
option (google.api.method_signature) = "parent,namespace,namespace_id";
} gapic-generator-python/gapic/schema/wrappers.py Lines 624 to 630 in 5f4c300
gapic-generator-python/gapic/templates/%namespace/%name_%version/%sub/services/%service/client.py.j2 Lines 331 to 340 in 41fa725
|
Fixed by #443 |
https://aip.dev/client-libraries/4222
It looks like the generator is not adding variables declared in the
google.api.http
annotation to routing headers.https://github.com/googleapis/googleapis/blob/52701da10fec2a5f9796e8d12518c0fe574488fe/google/cloud/servicedirectory/v1beta1/registration_service.proto#L60-L65
See https://github.com/GoogleCloudPlatform/python-docs-samples/pull/3456/files#r412305714 for the modifications that need to be made to currently use the library.
Possibly related to #380.
Metadata should be added somewhere here (see this method for comparison))
The text was updated successfully, but these errors were encountered: