Skip to content

DM-42924: Document use of apdb-cli metadata. #170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 14, 2024
Merged

DM-42924: Document use of apdb-cli metadata. #170

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion doc/playbook.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -561,7 +561,16 @@ To restore the APDB to a clean state, add the ``--drop`` option to ``apdb-cli c
Checking the APDB Version
-------------------------

To identify which schema and ApdbSql version a PostgreSQL APDB is using, run, e.g.:
If you have credentials for `rubin-pp-dev-users` configured (see `Buckets`_), you can identify an APDB's schema and ApdbSql/ApdbCassandra versions with ``apdb-cli``.
For example:

.. code-block:: sh

apdb-cli metadata show label:pp-dev:latiss:sql

See ``apdb-cli list-index`` for a list of valid labels.

For a PostgreSQL APDB, you can do the check without bucket access by running, e.g.:

.. code-block:: sh

Expand Down