Manage services from the CLI

Services are the databases and caches running on your servers — MySQL, PostgreSQL, MariaDB, Valkey, and the like. You can list them, inspect one in detail, and retire one you no longer need, all from the terminal.

List the services on a server

strackt service:list --server stk-abc12345

You'll see each service on that server with its type and current state. Narrow the list to one kind with --type:

strackt service:list --server stk-abc12345 --type valkey

Listing is per-server, so --server is required. Run it in a script or pass --json to get machine-readable output.

Inspect one service

strackt service:show --service 746e5d20-710a-4da2-b71f-52f83e14f001

This shows the full picture: the service's state, which server it's on, what's currently using it, the data it holds, and — if it can't be removed yet — exactly what's standing in the way. Reach for this when a service looks stuck, or before you retire one.

If you leave off --service in an interactive terminal, the CLI walks you through picking a server and then the service. In scripts, pass --service directly.

Retire a service

strackt service:retire --service 746e5d20-710a-4da2-b71f-52f83e14f001

Retiring removes the service from its server. It's destructive, so in a terminal the CLI asks you to confirm first. Skip the prompt when you're scripting:

strackt service:retire --service 746e5d20-710a-4da2-b71f-52f83e14f001 --force

By default a service is only retired once it's safe to — nothing depending on it, no work in flight. If you've checked with service:show and want to retire it anyway, override the safety checks:

strackt service:retire --service 746e5d20-710a-4da2-b71f-52f83e14f001 --skip-safety-checks

Retirement runs in the background. The command returns as soon as it's accepted and the service moves to retiring. Check back with service:show to watch it finish — or to see the reason if it stops partway.

What you need

• A token with service permission. If your token was created before service management was available, you'll get a permission error — create a fresh one with strackt auth:token and try again.
• The server's identifier for service:list (for example stk-abc12345), or a service's id for service:show / service:retire. service:list gives you the ids.

Good to know

• Listing is server-scoped. There's no single fleet-wide list yet — point service:list at one server at a time.
• Retirement is asynchronous. service:retire hands the work off and returns; service:show is how you follow it to completion (or find out why it's stuck).
• --skip-safety-checks is a last resort. It bypasses the checks that protect a service that's still in use. Look at service:show first.