App engine deployments with endpoint best practices

[Lance Myrick]

All, just wondering if anyone has some best practices for deploying an app engine flexible api implementation with an endpoint?  I have read the api appengine docs from googles site.

The clunkiness I have run into is there does not seem to be a good way to build and deploy the endpoints and app engine code at the same time as the endpoints_api_service>config_id parameter of the app.yaml file needs to be populated from the service-management config_id once the endpoint is deployed which is done by the glcoud service-management command not the maven deploy phase.

Our API implementation is a java maven project.  We are using the swagger maven plugin to generate the openapi.json file at build time.  Right now our jenkins job builds and deploys the endpoint only if there is a change to the openapi.json file, then grabs the config_id just created and populates the app.yaml file, after that we deploy the API code to app engine.  This process is simple enough; however, it feels clunky.  When I saw the maven appengine plugin I assumed that the plugin would handle not only the app engine api implementation but also the endpoints, this is not the case.

Am I missing something?

Thanks,  Lance

[Jordan (Cloud Platform Support)]

Google Cloud Endpoints allows you to choose your own framework to configure your API. You specifically chose the Open API specification, but you could have alternatively chose to use the provided Google Cloud Java Endpoints Framework. 

Note, if you require specific technical support for Cloud Endpoints, it is suggested to post your technical questions on Stack Overflow using the supported Google Cloud tags.