Endpoints portal error for proto file descriptor with google/api/field_behavior.proto

[Oscar Söderlund]

The service is successfully deployed with a proto file descriptor set, and the ESPv2 is successfully routing traffic.

When opening the endpoints portal to browse the API, the following error is given:

API parse error: Error: ENOENT: no such file or directory, open '/tmp/google/api/field_behavior.proto'

The issue looks similar to https://groups.google.com/g/google-cloud-endpoints/c/MJ6aOWHyp3g/m/SOLrU3FdDAAJ except that the issue is not with the local proto path. I've inspected the uploaded file descriptor set and it does indeed contain google/api/field_behavior.proto.

Since the service was successfully uploaded, and the traffic routing is working, can this be attributed specifically to the endpoints portal? Has anyone seen anything similar?

[Dan Massey]

Yes, I've got an API with annotations from google/api/annotations.proto, which I've got in my local environment.

The API deploys, serves fine, and ESPv2 is also carrying out gRPC/JSON translation, as described by the options that depend on the annotations.proto file.

However, in the API portal, I see this error:

API parse error: Error: ENOENT: no such file or directory, open '/tmp/google/api/httpbody.proto'

--
You received this message because you are subscribed to the Google Groups "Google Cloud Endpoints" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-endp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-endpoints/fed13a58-573e-4c3f-9f62-81536c80fea6n%40googlegroups.com.

--

Dan Massey

Product, Engineering & Data

(415) 890-4117

nomnomnow.com

Instagram | Facebook | Twitter

[Rob Wyrick]

+Alan Peters 

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-endpoints/CAOyfEGTe2QR89ipU5mMSL5S2QB%2B%3DW_YejxWXDUKV46X-s4nqeA%40mail.gmail.com.