Out Plane
domain

domain list

List the team's custom domains.

read onlyrepeatable

Every custom domain in the team, with the application and port each one reaches.

A host can appear more than once, once per path. The host and the path together are what identify a route. A route with no application is registered and answering nothing.

Usage

outplane domain list [flags]

Flags

FlagTypeDescription
--appstringOnly the routes going to this application.

The global flags apply as well.

Output

FieldTypeDescription
idstring | null
hoststring
pathstringTrailing slashes are stripped; the root is /.
appstring | nullNull while the route points nowhere.
appIdstring | null
portIdstring | nullThe port record the route binds to.
sslboolAlways true: a certificate is issued for every custom domain.
urlstring | nullThe address the route answers on.

Examples

Every domain in the team

outplane domain list

What one application answers on

outplane domain list --app checkout

Read the routes in a pipeline

outplane domain list --json --fields host,path,app
{
  "items": [
    {
      "app": "checkout",
      "host": "app.example.com",
      "path": "/"
    }
  ],
  "total": 1,
  "truncated": false
}

What to Know

  • One host can appear several times, once per path. The pair identifies a route; the host alone does not.
  • app is null for a route that points nowhere. It is registered, holds the host, and answers nothing.

Errors

Beyond 0 for success, this command exits with:

ExitKindMeaning
2usageInvalid arguments, unknown flag, or client-side validation failure.
3authNot authenticated, token revoked or expired, or forbidden for this team.
5not_foundThe named resource does not exist, or is not visible to this credential.
8upstreamThe Out Plane API returned a server error.

The code on the error object is one of app.not_found, context.no_team. Branch on that, or on the exit status. The message is prose and changes.

On this page