Swagger Codegen With Multiple Additional Bindings is resulting in missing Documentation

[bandikishores]

In a proto if we define a service with 2 rpc's, both having an additional_bindings then only the last additional_bindings is being honored while generating swagger documentation. The other rpc's additional bindings are totally missing.

service UserService {
  rpc DeleteUser(DeleteUserRequest) returns (DeleteUserResponse){
      option (google.api.http) = {
          delete: "/organizations/{orgName}/users/{name}"
          additional_bindings {
              get: "/users/{name}"
          }
      };
  }

  rpc StreamUsers(GetUserRequest) returns (stream GetUserResponse){
      option (google.api.http) = {
          get: "/organizations/{orgName}/streamusers/{name}"
          additional_bindings {
              get: "/users/{name}"
          }
      };
  }
}

The corresponding Swagger generated contains only one Alternative Binding (StreamUser2 is present, binding for DeleteUser2 is missing).

{
    "swagger": "2.0",
    ...,
    "paths": {
      "/organizations/{orgName}/streamusers/{name}": {
        "get": {
          "operationId": "StreamUsers",
          "responses": {
            "200": {
              "description": "A successful response.(streaming responses)",
              "schema": {
            ...,
        "delete": {
          "operationId": "DeleteUser",
          "responses": {
            "200": {
              "description": "A successful response.",
              "schema": {
            ...,
      "/users/{name}": {
        "get": {
          "operationId": "StreamUsers2",
          "responses": {
            "200": {
              "description": "A successful response.(streaming responses)",
              "schema": {
  }

Sample Proto File is available here
Sample Swagger Json is available here

[bandikishores]

This issue was because both the bindings had the same option & path. Closing the issue.