Firebase App Hosting streamlines the development and deployment of dynamic Next.js and Angular applications, offering built-in framework support, GitHub integration, and integration with other Firebase products. You can use this API to intervene in the Firebase App Hosting build process and add custom functionality not supported in our default Console & CLI flows, including triggering builds from external CI/CD workflows or deploying from pre-built container images.

A backend is the primary resource of App Hosting.

A single build for a backend, at a specific point codebase reference tag and point in time. Encapsulates several resources, including an Artifact Registry container image, a Cloud Build invocation that built the image, and the Cloud Run revision that uses that image.

The source for the build.

The request message for Operations.CancelOperation.

The connection to an external source repository to watch for event-driven updates to the backend.

A codebase source, representing the state of the codebase that the build will be created at.

Additional configuration of the backend for this build.

The URI of an Artifact Registry container image to use as the build source.

Defines the root interface for all clients that generate credentials for calling Google APIs. All clients should implement this interface.

Additional metadata for operations on custom domains.

The status of a custom domain's linkage to a backend.

A representation of a DNS records for a domain. DNS records are resource records that define how systems and services should behave when handling requests for a domain. For example, when you add A records to your domain's DNS records, you're informing other systems (such as your users' web browsers) to contact those IPv4 addresses to retrieve resources relevant to your domain (such as your App Hosting files).

A set of DNS records relevant to the setup and maintenance of a custom domain in App Hosting.

A set of DNS record updates that you should make to allow App Hosting to serve secure content in response to requests against your domain. These updates present the current state of your domain's and related subdomains' DNS records when App Hosting last queried them, and the desired set of records that App Hosting needs to see before your custom domain can be fully active.

A domain name that is associated with a backend.

Represents the metadata of a long-running operation on domains.

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); }

Environment variables for this build.

The container for the rpc status and source for any errors found during the build process.

Message for response to list backends

Message for response to list builds.

Message for response to list domains.

The response message for Locations.ListLocations.

The response message for Operations.ListOperations.

Message for response to list rollouts.

A set of updates including ACME challenges and DNS records that allow App Hosting to create an SSL certificate and establish project ownership for your domain name before you direct traffic to App Hosting servers. Use these updates to facilitate zero downtime migrations to App Hosting from other services. After you've made the recommended updates, check your custom domain's ownershipState and certState. To avoid downtime, they should be OWNERSHIP_ACTIVE and CERT_ACTIVE, respectively, before you update your A and AAAA records.

A resource that represents a Google Cloud location.

An external resource managed by App Hosting on the project.

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

Represents the metadata of a long-running operation.

Additional options for FirebaseAppHosting#projectsLocationsBackendsBuildsCreate.

Additional options for FirebaseAppHosting#projectsLocationsBackendsBuildsDelete.

Additional options for FirebaseAppHosting#projectsLocationsBackendsBuildsList.

Additional options for FirebaseAppHosting#projectsLocationsBackendsCreate.

Additional options for FirebaseAppHosting#projectsLocationsBackendsDelete.

Additional options for FirebaseAppHosting#projectsLocationsBackendsDomainsCreate.

Additional options for FirebaseAppHosting#projectsLocationsBackendsDomainsDelete.

Additional options for FirebaseAppHosting#projectsLocationsBackendsDomainsList.

Additional options for FirebaseAppHosting#projectsLocationsBackendsDomainsPatch.

Additional options for FirebaseAppHosting#projectsLocationsBackendsList.

Additional options for FirebaseAppHosting#projectsLocationsBackendsPatch.

Additional options for FirebaseAppHosting#projectsLocationsBackendsRolloutsCreate.

Additional options for FirebaseAppHosting#projectsLocationsBackendsRolloutsList.

Additional options for FirebaseAppHosting#projectsLocationsBackendsTrafficPatch.

Additional options for FirebaseAppHosting#projectsLocationsList.

Additional options for FirebaseAppHosting#projectsLocationsOperationsList.

Specifies redirect behavior for a domain.

A single rollout of a build for a backend.

The policy for how automatic builds and rollouts are triggered and rolled out.

Additional configuration to apply to the Cloud Run service.

A managed Cloud Run service.

Indicates whether App Hosting will serve content on the domain.

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.

Controls traffic configuration for the backend.

A list of traffic splits that together represent where traffic is being routed.

The traffic allocation for the backend.

Version control metadata for a user associated with a resolved codebase. Currently assumes a Git user.