eve-cli-primitives

Eve CLI Primitives

Use this skill as the command map for Eve. Keep examples short and concrete.

Profiles (API Target + Defaults)

# Create and use a profile
eve profile create staging --api-url https://api.eve.example.com
eve profile use staging

# Set defaults to avoid repeating flags
eve profile set --default-email [email protected] --default-ssh-key ~/.ssh/id_ed25519
eve profile set --org org_xxx --project proj_xxx

# Inspect current profile
eve profile show

Authentication

eve auth login
eve auth status
eve auth logout
eve auth permissions

# Sync local OAuth tokens for agent harnesses (optional)
eve auth sync

# Nostr challenge (API-level, no CLI command yet)
# POST /auth/challenge {"provider": "nostr", "pubkey": "<hex>"}

Orgs and Projects

eve org list
eve org ensure my-org --slug myorg

eve project list
eve project ensure --name "My App" --slug my-app --repo-url [email protected]:me/my-app.git --branch main

# Membership management
eve org members --org org_xxx
eve org members add [email protected] --role admin --org org_xxx
eve org members remove user_abc --org org_xxx

eve project members --project proj_xxx
eve project members add [email protected] --role admin --project proj_xxx
eve project members remove user_abc --project proj_xxx

URL impact: The org --slug and project --slug directly form your deployment URLs and K8s namespaces:

• URL: {service}.{orgSlug}-{projectSlug}-{env}.{domain} (e.g., api.myorg-my-app-staging.eve.example.com)
• Namespace: eve-{orgSlug}-{projectSlug}-{env} (e.g., eve-myorg-my-app-staging)

Choose slugs carefully — they are immutable after creation.

Environments and Deploys

# Create a persistent environment
eve env create staging --project proj_xxx --type persistent

# Inspect environments
eve env list --project proj_xxx
eve env show staging --project proj_xxx

# Deploy an environment (requires --ref with 40-char SHA or a ref resolved against --repo-dir)
eve env deploy staging --ref main --repo-dir .

# When environment has a pipeline configured, the above triggers the pipeline.
# Use --direct to bypass pipeline and deploy directly:
eve env deploy staging --ref main --repo-dir . --direct

# Pass inputs to pipeline:
eve env deploy staging --ref main --repo-dir . --inputs '{"key":"value"}'

# Diagnostics
eve env diagnose proj_xxx staging
eve env diagnose proj_xxx staging --request <req_id>     # request-level integrated diagnose
eve env logs proj_xxx staging <service>
eve env logs proj_xxx staging <service> --follow         # stream logs
eve env logs proj_xxx staging <service> --filter route=/api/x --filter status=500
eve env delete proj_xxx staging