overlane inbox preferences

Prints, for each kind of event (ci_failed, deploy_failed, deploy_rolled_back, approval_requested, alert_fired, run_error, digest, import_finished), whether you are told in the app, by email or not at all. A kind you never chose is told in the app.

Usage

overlane inbox preferences [--service URL]

Flags

Flag	Type	Required	Default	Description
`--service`	string	no		The service address (default: OVERLANE_SERVICE_URL, then the project’s binding, then the hosted service)

Examples

overlane inbox preferences
overlane inbox preferences --json

Behavior

Effect: read (changes nothing).
Needs credentials: yes. Uses the network: yes.
Supports --dry-run: no. Accepts --force: no.
Machine-readable description: overlane schema inbox preferences.

Result

With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.

{
  "type": "object",
  "properties": {
    "preferences": {
      "type": "object",
      "propertyNames": {
        "type": "string",
        "enum": [
          "ci_failed",
          "deploy_failed",
          "deploy_rolled_back",
          "approval_requested",
          "alert_fired",
          "run_error",
          "digest",
          "import_finished"
        ]
      },
      "additionalProperties": {
        "type": "string",
        "enum": [
          "in_app",
          "email",
          "none"
        ]
      },
      "required": [
        "ci_failed",
        "deploy_failed",
        "deploy_rolled_back",
        "approval_requested",
        "alert_fired",
        "run_error",
        "digest",
        "import_finished"
      ]
    }
  },
  "required": [
    "preferences"
  ],
  "additionalProperties": false
}

See exit codes for the status the process returns.