OpenAPI document

Related topics

• API Gateway works with OpenAPI document From the official documentation: “API Gateway supports APIs that are described using [supported versions](#supported-openapi-versions) of the OpenAPI specification.”
• Cloud Endpoints depends on OpenAPI document From the official documentation: “You need the Endpoints Frameworks library and the OpenAPI document so that Endpoints can manage the API.”
• Extensible Service Proxy V2 works with OpenAPI document From the official documentation: “ESPv2 supports version 2 of the [OpenAPI Specification](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md) and [gRPC](http://www.grpc.io) Specifications.”
• OpenAPI document configures API Gateway From the official documentation: “You can use an OpenAPI specification that contains specialized extensions to define the chosen API Gateway behavior.”
• OpenAPI document configures Cloud Endpoints From the official documentation: “Configure the `openapi.yaml` file, which is used to configure Endpoints.”
• Extensible Service Proxy is an alternative to Extensible Service Proxy V2 From the official documentation: “ESPv2 is a drop-in replacement for ESP.”
• API Gateway works with Cloud Run From the official documentation: “API Gateway only supports Cloud Run gRPC services at this time.”
• Cloud Run works with Extensible Service Proxy V2 From the official documentation: “Deploy the ESPv2 Cloud Run service with the new image you built above.”
• Cloud Endpoints works with Compute Engine From the official documentation: “Getting started with Endpoints on Compute Engine”
• Cloud Endpoints depends on Service Management API From the official documentation: “Cloud Endpoints uses Service Management to manage your API.”
• Cloud Trace works with Extensible Service Proxy V2 From the official documentation: “When a request is received, ESP or ESPv2 creates a trace token for Cloud Trace.”
• Compute Engine works with Extensible Service Proxy From the official documentation: “Learn how to configure, deploy, and issue requests against a sample API and ESP using an instance running in Compute Engine.”
• Compute Engine works with Extensible Service Proxy V2 From the official documentation: “Learn how to configure, deploy, and issue requests against a sample API and ESPv2 running in Compute Engine in a Docker container.”
• API Gateway secures Cloud Functions From the official documentation: “Deploy an API on API Gateway to secure traffic to a Cloud Functions backend using the Google Cloud CLI.”
• Cloud Endpoints works with Cloud Run From the official documentation: “In addition, Endpoints only supports gRPC services for GKE, Compute Engine, and Cloud Run (Beta).”
• Cloud Endpoints depends on Extensible Service Proxy From the official documentation: “Endpoints for OpenAPI depends on either ESP or ESPv2 for API management.”
• Cloud Endpoints works with Extensible Service Proxy From the official documentation: “Enabling SSL with ESP Shows how to enable an SSL port for your deployed Endpoints service using ESP.”
• Cloud Endpoints works with Extensible Service Proxy V2 From the official documentation: “Enabling SSL for Cloud Endpoints with ESPv2”
• Extensible Service Proxy V2 is part of Cloud Endpoints From the official documentation: “The components that make up Endpoints are: - Extensible Service Proxy (ESP) or Extensible Service Proxy V2 (ESPv2) - for injecting Endpoints functionality.”
• Extensible Service Proxy V2 depends on Service Management API From the official documentation: “At a minimum, Endpoints and ESP require the following Google services to be enabled: | Name | Title | | --- | --- | | `servicemanagement.googleapis.com` | Service Management API |”
• API Gateway works with Cloud Endpoints From the official documentation: “Deploying Cloud Endpoints APIs on API Gateway Describes how to try your Cloud Endpoints APIs on API Gateway.”
• API Gateway works with Cloud Functions From the official documentation: “The steps required to set up API Gateway to manage and secure a [Cloud Functions](/functions/docs) backend service are outlined in the API Gateway [Quickstarts](/api-gateway/docs/quickstarts).”
• API Gateway secures Cloud Run From the official documentation: “This page shows you how to set up API Gateway to manage and secure a [Cloud Run](/run/docs) backend service with gRPC.”
• API Gateway works with Cloud Trace From the official documentation: “API Gateway creates a trace token for Cloud Trace.”
• API Gateway depends on Service Management API From the official documentation: “API Gateway requires that you enable the following Google services: | Name | Title | | --- | --- | | `apigateway.googleapis.com` | API Gateway API | | `servicemanagement.googleapis.com` | Service Management API |”
• Cloud Endpoints depends on Extensible Service Proxy V2 From the official documentation: “Endpoints for OpenAPI depends on either ESP or ESPv2 for API management.”
• Cloud Endpoints works with Service Management API From the official documentation: “To deploy the Endpoints configuration, you use the [gcloud endpoints services deploy](/sdk/gcloud/reference/endpoints/services/deploy) command. This command uses [Service Management](/service-infrastructure/docs/manage-config) to create a managed service.”
• Cloud Functions depends on Cloud Run From the official documentation: “Cloud Run functions represent the next evolution of Cloud Functions, offering an event-driven programming model with enhanced control and scalability, leveraging the Cloud Run serverless platform.”
• Cloud Functions works with Extensible Service Proxy V2 From the official documentation: “Grant ESPv2 permission to invoke your functions.”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run works with Extensible Service Proxy From the official documentation: “This may happen when deploying ESPv2 in Cloud Run, the flag `--allow-unauthenticated` is not used in `gcloud run deploy` command.”
• Cloud Trace works with Extensible Service Proxy From the official documentation: “When a request is received, ESP or ESPv2 creates a trace token for Cloud Trace.”
• Extensible Service Proxy is part of Cloud Endpoints From the official documentation: “The components that make up Endpoints are: - Extensible Service Proxy (ESP) or Extensible Service Proxy V2 (ESPv2) - for injecting Endpoints functionality.”
• Extensible Service Proxy depends on Service Management API From the official documentation: “Upon startup, ESP or ESPv2 obtains its service configuration from Service Management.”
• Extensible Service Proxy V2 depends on Cloud Run From the official documentation: “To provide API management for App Engine, you deploy the prebuilt ESPv2 container to [Cloud Run](/run/docs).”
• Service Management API is part of Cloud Endpoints From the official documentation: “The components that make up Endpoints are: - Extensible Service Proxy (ESP) or Extensible Service Proxy V2 (ESPv2) - for injecting Endpoints functionality. - Service Control - for applying API management rules. - Service Management - for configuring API management rules.”