db-status

Name: db-status
Availability: InStock
Author: Lablup

Report current and head Alembic migration revisions for Backend.AI components.

662|179|Updated Oct 6, 2016

Search Tags:#database #migration #diagnostics #status #alembic #backend.ai

Ready to run

npx skills add https://github.com/lablup/backend.ai --skill db-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: db-status
Source: https://github.com/lablup/backend.ai/tree/main/.claude/skills/db-status
Command: npx skills add https://github.com/lablup/backend.ai --skill db-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides visibility into the migration state of the Backend.AI databases across its core components (manager, accountmgr, appproxy), enabling proactive maintenance and troubleshooting.

Core Features & Use Cases

Migration status checks: Retrieve current and head revisions for each component's Alembic setup.
Cross-component health: Verify consistency of migrations when updating code across manager, accountmgr, and appproxy.
Use Case: Before applying migrations, run this skill to confirm pending changes and target the correct component.

Quick Start

Run the default status check for the manager database:

/db-status Check a specific component:
/db-status --component=appproxy Check all components:
/db-status --component=manager --all

Frequently Asked Questions about db-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check Alembic database migration status across Backend.AI components?▼

To check Alembic database migration status, run a status command to retrieve current and head revisions for Backend.AI manager, accountmgr, and appproxy components. This verifies migration consistency and identifies pending changes across your deployment.

What is the best way to perform a pre-migration check for Backend.AI manager databases?▼

A pre-migration check for Backend.AI manager databases involves querying the Alembic configuration to report the current revision and target head revision. This process highlights pending migrations, allowing you to confirm necessary changes before applying them.

Can I verify cross-component migration consistency for manager, accountmgr, and appproxy?▼

Yes, you can verify cross-component migration consistency by checking Alembic revisions across manager, accountmgr, and appproxy simultaneously. This confirms all Backend.AI components are aligned at the correct migration head before a code update.

How do I retrieve current and head revisions for a specific Backend.AI component like appproxy?▼

To retrieve current and head revisions for a specific component like appproxy, execute the status command with the component flag specified. This queries the appproxy Alembic setup to return its exact migration state.

Does Backend.AI database migration tracking require Alembic configurations to run?▼

Yes, Backend.AI database migration tracking requires Alembic configurations and command execution to retrieve current and head revisions. The system depends on Alembic to determine the migration status for each component.