google_api_app_engine v0.0.1 API Reference
Modules
API calls for all endpoints tagged Apps
Handle Tesla connections for GoogleApi.AppEngine.V1
Helper functions for deserializing responses into models
Google Cloud Endpoints (https://cloud.google.com/appengine/docs/python/endpoints/) configuration for API handlers
Uses Google Cloud Endpoints to handle requests
An Application resource contains the top-level configuration of an App Engine application. Next tag: 20
Automatic scaling is based on request rate, response latencies, and other application metrics
A service with basic scaling will create an instance when the application receives a request. The instance will be turned down when the app becomes idle. Basic scaling is ideal for work that is intermittent or driven by user activity
Docker image that is used to create a container and start a VM instance for the version that you deploy. Only applicable for instances running in the App Engine flexible environment
Target scaling by CPU usage
Request message for Instances.DebugInstance
Code and application artifacts used to deploy a version to App Engine
Target scaling by disk usage. Only applicable for VM runtimes
Cloud Endpoints (https://cloud.google.com/endpoints) configuration. The Endpoints API Service provides tooling for serving Open API and gRPC endpoints via an NGINX proxy.The fields here refer to the name and configuration id of a "service" resource in the Service Management API (https://cloud.google.com/service-management/overview)
Custom static error page to be served when an error occurs
The feature specific settings to be used in the application. These define behaviors that are user configurable
Single source file that is part of the version to be deployed. Each source file that is deployed must be specified separately
Health checking configuration for VM instances. Unhealthy instances are killed and replaced with new instances. Only applicable for instances in App Engine flexible environment
Identity-Aware Proxy
An Instance resource is the computing unit that App Engine uses to automatically scale an application
Third-party Python runtime library that is required by the application
Response message for Instances.ListInstances
The response message for Locations.ListLocations
The response message for Operations.ListOperations
Response message for Services.ListServices
Response message for Versions.ListVersions
Health checking configuration for VM instances. Unhealthy instances are killed and replaced with new instances
A resource that represents Google Cloud Platform location
Metadata for the given google.cloud.location.Location
A service with manual scaling runs continuously, allowing you to perform complex initialization and rely on the state of its memory over time
Extra network settings. Only applicable for App Engine flexible environment versions
Target scaling by network usage. Only applicable for VM runtimes
This resource represents a long-running operation that is the result of a network API call
Metadata for the given google.longrunning.Operation
Metadata for the given google.longrunning.Operation
Metadata for the given google.longrunning.Operation
Metadata for the given google.longrunning.Operation
Metadata for the given google.longrunning.Operation
Metadata for the given google.longrunning.Operation
Readiness checking configuration for VM instances. Unhealthy instances are removed from traffic rotation
Request message for 'Applications.RepairApplication'
Target scaling by request utilization. Only applicable for VM runtimes
Machine resources for a version
Executes a script to handle the request that matches the URL pattern
A Service resource is a logical component of an application that can share state and communicate in a secure fashion with other services. For example, an application that handles customer requests might include separate services to handle tasks such as backend data analysis or API requests from mobile devices. Each service has a collection of versions that define a specific set of code used to implement the functionality of that service
Files served directly to the user for a given URL, such as images, CSS stylesheets, or JavaScript source files. Static file handlers describe which files in the application directory are static files, and which URLs serve them
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC (https://github.com/grpc). The error model is designed to be: Simple to use and understand for most users Flexible enough to meet unexpected needsOverviewThe Status message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package google.rpc that can be used for common error conditions.Language mappingThe Status message is the logical representation of the error model, but it is not necessarily the actual wire format. When the Status message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C.Other usesThe error model and the Status message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments.Example uses of this error model include: Partial errors. If a service needs to return partial errors to the client, it may embed the Status in the normal response to indicate the partial errors. Workflow errors. A typical workflow has multiple steps. Each step may have a Status message for error reporting. Batch operations. If a client uses batch request and batch response, the Status message should be used directly inside batch response, one for each error sub-response. Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the Status message. Logging. If some API errors are stored in logs, the message Status could be used directly after any stripping needed for security/privacy reasons
Traffic routing configuration for versions within a single service. Traffic splits define how traffic directed to the service is assigned to versions
Rules to match an HTTP request and dispatch that request to a service
URL pattern and description of how the URL should be handled. App Engine can handle URLs by executing application code or by serving static files uploaded with the version, such as images, CSS, or JavaScript
A Version resource is a specific set of source code and configuration files that are deployed into a service
Volumes mounted within the app container. Only applicable for VM runtimes
The zip file information for a zip deployment
Helper functions for building Tesla requests