google_endpoints_service only allows to specify 1 compiled .pb file

[svenschwermer]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

google_endpoints_service only allows to specify one protoc compiled descriptor file (protoc_output_base64). Neither the underlying API nor the gcloud endpoints services deploy command have this limitation.

New or Affected Resource(s)

• google_endpoints_service

Potential Terraform Configuration

resource "google_endpoints_service" "grpc_service" {
  // ...
  protoc_output_base64 = [
    base64encode(file("compiled_descriptor_file_1.pb")),
    base64encode(file("compiled_descriptor_file_2.pb")),
  ]
  // ...
}

References

• N/A

b/356678270

[adambabik]

I hit this issue today but there is an easy workaround - compile all your Protobufs into a single file descriptor (.pb file). I believe it might be a recommended approach actually as executing gcloud endpoints services deploy with one API config YAML file and multiple file descriptor was failing for me (the error was "Cannot resolve api 'my.api.MyService'" as if one file descriptor was overwriting the other). On the other hand, gcloud endpoints services deploy usage suggests it's possible to provide multiple file descriptors...

[jos-]

Related to this: it's impossible to set multiple grpc_config files, which is possible using gcloud and the underlying API.

Currently, the only workaround seems to be to use local-exec in combination with gcloud.

[roaks3]

Assuming this is feasible since it is already an option in gcloud