Namespace Google.Apis.FirebaseDataConnect.v1beta.Data

Classes

CancelOperationRequest

The request message for Operations.CancelOperation.

CloudSqlInstance

Settings for CloudSQL instance configuration.

Connector

Connector consists of a set of operations, i.e. queries and mutations.

Datasource

A data source that backs Firebase Data Connect services.

Empty

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

ExecuteMutationRequest

The ExecuteMutation request to Firebase Data Connect.

ExecuteMutationResponse

The ExecuteMutation response from Firebase Data Connect.

ExecuteQueryRequest

The ExecuteQuery request to Firebase Data Connect.

ExecuteQueryResponse

The ExecuteQuery response from Firebase Data Connect.

File

Individual files.

GraphqlError

GraphqlError conforms to the GraphQL error spec. https://spec.graphql.org/draft/#sec-Errors Firebase Data Connect API surfaces GraphqlError in various APIs: - Upon compile error, UpdateSchema and UpdateConnector return Code.Invalid_Argument with a list of GraphqlError in error details. - Upon query compile error, ExecuteGraphql and ExecuteGraphqlRead return Code.OK with a list of GraphqlError in response body. - Upon query execution error, ExecuteGraphql, ExecuteGraphqlRead, ExecuteMutation and ExecuteQuery all return Code.OK with a list of GraphqlError in response body.

GraphqlErrorExtensions

GraphqlErrorExtensions contains additional information of GraphqlError.

GraphqlRequest

The GraphQL request to Firebase Data Connect. It strives to match the GraphQL over HTTP spec. https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md#post

GraphqlRequestExtensions

GraphqlRequestExtensions contains additional information of GraphqlRequest.

GraphqlResponse

The GraphQL response from Firebase Data Connect. It strives to match the GraphQL over HTTP spec. Note: Firebase Data Connect always responds with Content-Type: application/json. https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md#body

Impersonation

Impersonation configures the Firebase Auth context to impersonate.

ListConnectorsResponse

Message for response to listing Connectors. By default, connectors.source will not be included in the response. To specify the fields included in the response, the response field mask can be provided by using the query parameter $fields or the header X-Goog-FieldMask.

ListLocationsResponse

The response message for Locations.ListLocations.

ListOperationsResponse

The response message for Operations.ListOperations.

ListSchemasResponse

Message for response to listing Schemas. By default, schemas.source will not be included in the response. To specify the fields included in the response, the response field mask can be provided by using the query parameter $fields or the header X-Goog-FieldMask.

ListServicesResponse

Message for response to listing Services.

Location

A resource that represents a Google Cloud location.

Operation

This resource represents a long-running operation that is the result of a network API call.

OperationMetadata

Represents the metadata of the long-running operation. Note: This message is auto-generated by CCFE. CCFE's storage, called Resource Metadata Store (RMS), holds metadata about long-running operations (i.e. OperationMetadata) and resources (i.e. ResourceMetadata). OperationMetadata documents the status of the operation. See CCFE documentation for sidechannel data and yaqs/4289526912465764352.

PostgreSql

Settings for PostgreSQL data source.

Schema

The application schema of a Firebase Data Connect service.

Service

A Firebase Data Connect service.

Source

Used to represent a set of source files.

SourceLocation

SourceLocation references a location in a GraphQL source.

Status

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. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.