For a HTTP endpoint that has various parameters held in objects, you can only see one parameter, after this, the second one will not appear on the Cloud Endpoints Portal UI. However, using the API works as expected.
Documentation of this procedure can be found here [1].
What you expected to happen:
All parameters should appear in the Cloud Endpoints Portal UI.
Steps to reproduce:
After generating the descriptior.pb file and deploying it with the gcloud endpoint service command [2] the issue can be reproduced and the second object field which is the destination message doesn't get displayed in the Endpoints portal.
Description
For a HTTP endpoint that has various parameters held in objects, you can only see one parameter, after this, the second one will not appear on the Cloud Endpoints Portal UI. However, using the API works as expected.
Documentation of this procedure can be found here [1].
What you expected to happen:
All parameters should appear in the Cloud Endpoints Portal UI.
Steps to reproduce:
After generating the descriptior.pb file and deploying it with the gcloud endpoint service command [2] the issue can be reproduced and the second object field which is the destination message doesn't get displayed in the Endpoints portal.
_________________________
[1]:
[2]: gcloud endpoints services deploy api_descriptor.pb api_config.yaml" command.