Databases and cron jobs

edka databases and edka cronjobs work with the databases and cron jobs of the linked cluster, or of the one --cluster names. Without a linked cluster, list shows those of every cluster. To create them, use the console, as Databases and Cron Jobs describe, or the API commands.

Prerequisites

• The Edka CLI, signed in with edka login.

Databases

edka databases list
edka databases get orders                # Instances, primary and recovery window
edka databases backup orders             # Start a backup now
edka databases backups orders            # Backups, newest first
edka databases logs orders --follow
edka databases diagnose orders           # Instances, archiving and backups that fail
edka databases delete orders

backups lists a database’s backups, newest first. For PostgreSQL, it lists the ten most recent. logs takes the flags of edka logs, such as --pod, --previous and --tail.

delete deletes a database with its data, and asks you to type its name. Edka refuses while an app uses the database or while it is still provisioning, and --force deletes it anyway.

See Diagnose problems for what databases diagnose finds.

Cron jobs

edka cronjobs list
edka cronjobs get nightly-report         # The cron job and its last run
edka cronjobs runs nightly-report        # Recent runs, newest first
edka cronjobs trigger nightly-report     # Start a run now
edka cronjobs logs nightly-report        # Logs of the newest run
edka cronjobs logs nightly-report --run nightly-report-29311
edka cronjobs suspend nightly-report     # Stop scheduled runs
edka cronjobs resume nightly-report
edka cronjobs diagnose nightly-report    # Why the last run failed, or why none starts
edka cronjobs delete nightly-report

runs lists the last 20 runs, and --limit up to 100. logs reads the newest run, or the one --run names from the list of runs. suspend stops the scheduled runs, and resume starts them again.

delete deletes the cron job and its Kubernetes resources, after confirmation or with --yes.