Deployments

gigadrive deployments reads deployment history for a Gigadrive Network application: what shipped, what failed, and which hostnames a given deployment answers on. It does not create deployments, which is Deploy.

Listing deployments

gigadrive deployments list

0195c22d-0000-7000-8000-000000000100  FAILED        2026-08-12T08:51:03.000Z
0195c22d-0000-7000-8000-000000000101  ACTIVE        2026-08-12T09:14:22.000Z

2 deployment(s).

Each line is the deployment ID, the status padded to twelve characters, then the creation timestamp. An empty result prints No deployments found.

Two things about that list are easy to misread. Rows come back in creation order, oldest first. And the CLI sends no page size and never asks for a second page, so you get the API's default page of ten while the trailing count reports every deployment matching your filters. 84 deployment(s). beneath ten rows is correct, and those rows are the oldest ten of the eighty-four rather than the newest. Narrow with --app and --status until ten rows say something, and watch live history in the console.

In a linked directory the linked application becomes the default filter. In an unlinked directory there is no application filter at all and the command lists across everything the account can see, so pass --app or --org when you mean one of them. A .gigadrive/project.json that exists but is malformed is an error rather than a silent fallback to the unfiltered query.

Status values

--status takes exactly one of these, uppercase. The parser rejects anything else before a request goes out.

gigadrive deployments list --status FAILED --org 0195c0aa-0000-7000-8000-0000000000ff

Inspecting one deployment

gigadrive deployments inspect takes a deployment ID and has no flags.

gigadrive deployments inspect 0195c22d-0000-7000-8000-000000000101

ID:          0195c22d-0000-7000-8000-000000000101
Application:  0195c11c-0000-7000-8000-000000000042
Status:      ACTIVE
Created:     2026-08-12T09:14:22.000Z
Updated:     2026-08-12T09:16:41.000Z
Hostnames:
  https://marketing-site-k4n2q.gigadrive.app
  https://marketing-site.gigadrive.app (inactive)

The Hostnames: block appears only when the deployment has hostnames. (inactive) marks a mapping that is recorded against the deployment but is not routable, so requests to it do not reach this build. If the hostname lookup itself fails, the command still prints the five standard fields and succeeds.

Neither subcommand streams build logs. gigadrive deploy prints them while a deployment runs, and finished logs stay in the console.