Organizations, Projects and Environments

The org/project/env pattern from the terminal.

Organizations#

BASH
zensailor org list                          # every org you belong to
zensailor org members list <org-id>
zensailor org members invite <org-id> --email dev@example.com
zensailor org members rm <org-id> --user <user-id>
zensailor org members set-role <org-id> --user <user-id> --role admin
zensailor org concurrency show <org-id>     # deployment slots
zensailor org concurrency set <org-id> 5    # plan-limited on Enterprise

Projects#

BASH
zensailor project list [org-id]
zensailor project create [org-id] --name bookings
zensailor project update <project-id> --name bookings-v2
zensailor project rm <project-id>           # confirm; deletes children

Environments#

BASH
zensailor env create <project-id> --name staging --type staging
zensailor env update <env-id> --name preprod
zensailor env clone <source-env-id>         # services + variables into a new env
zensailor env rm <env-id>

Environment variables#

BASH
# Scoped listing (project / environment / service)
zensailor env-var list --scope <project|environment|service> --id <id>
zensailor env-var set KEY=value ANOTHER=value
zensailor env-var rm KEY1 KEY2

Variables are resolved at deploy time downward (service over environment over project) — see Environment Variables and Secrets.