overlane deploy envs | Overlane Docs

Lists the project’s environments (such as staging and production) with the target each deploys to and whether it is protected, beside the targets. Secrets are never shown.

Usage

overlane deploy envs

Examples

overlane deploy envs
overlane deploy envs --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 deploy envs.

Result

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

{
  "type": "object",
  "properties": {
    "tenantId": {
      "type": "string"
    },
    "targets": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          }
        },
        "required": [
          "name"
        ],
        "additionalProperties": {}
      }
    },
    "environments": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "targetId": {
            "type": "string"
          },
          "protected": {
            "type": "boolean"
          }
        },
        "required": [
          "name",
          "targetId",
          "protected"
        ],
        "additionalProperties": {}
      }
    }
  },
  "required": [
    "tenantId",
    "targets",
    "environments"
  ],
  "additionalProperties": {}
}

See exit codes for the status the process returns.