Interacting with the registry database via pgAdmin

🌐 This document is available in both English and Ukrainian. Use the language toggle in the top right corner to switch between versions.

You can view changes in the registry database and work with tables and other data structures using the pgAdmin tool.

To do this, follow a few simple steps:

  1. Log into the Unresolved include directive in modules/registry-develop/pages/registry-admin/db-connection/db-connection-pgadmin.adoc - include::platform:ROOT:partial$templates/links/platform/administrative/control-plane.adoc[] administrative panel.

  2. Open Registries  Quick Links  Registry administrative zone. and follow the link to the Web interface for viewing registry data (pgAdmin).

    db connection pgadmin 1

    Alternative way to access

    1. Open the Openshift  Projects console and select your registry.

    2. Go to Networking  Routes, and in the search, find the route for the pgadmin service.

      review db changes before merge 17
    Where do you find the login and password for pgadmin?

    The login and password for pgadmin can be found in the Workloads  Secrets section, in the secret named pgadmin-secret.

    review db changes before merge 18

  3. (For logging in under the system role application_role) In the pgAdmin interface, find the Servers section and enter the password for the system user application_role to connect with the registry DB server.

    review db changes before merge 19

    Where do you find the password for connecting to the registry DB server?

    The password for connecting to the registry DB server Registry for the user application_role can be found in the Workloads  Secrets section, in secret named citrus-roles-secrets. Use the password from the appRolePass field.

    review db changes before merge 20

    review db changes before merge 21

  4. (For logging in as the registry owner with the role registry_owner_role) If you wish to log in as registry_owner_role (registry owner), change the server connection parameters for Registry. You can do this as follows:

    1. In the pgAdmin connection window, open Servers  Registry  Properties.

      db connection pgadmin 5

    2. On the Connection tab, set the Username parameter to registry_owner_role and save the changes.

      db connection pgadmin 6

      The password for connecting to the registry DB server Registry for the user registry_owner_role can be found in the Workloads  Secrets section, in secret named citrus-roles-secrets. Use the password from the regOwnerPass field.

      review db changes before merge 20

  5. Locate the operational database registry and review the changes. It can be accessed via:
    Servers  Registry  Databases  registry.

    db connection pgadmin 2

    Details on viewing data in temporary databases are described on the page registry-develop:best-practices/review-db-changes-before-merge.adoc.

    • Created tables can be viewed via: Schemas  registry  Tables.

      db connection pgadmin 3

    • Created search conditions can be viewed via: Schemas  registry  Views.

      db connection pgadmin 4

      Search criteria in the database are view tables (VIEW), intended solely for reading data. The naming convention for search conditions at the data model and DB levels coincides, with the only exception being that a suffix _v is added to the name of each search criterion in the DB.

      For example, if you created a search condition named get_parent_by_name, then in the database, this name transforms into get_parent_by_name_v.