Skip to content

docs(keycloak): document local PostgreSQL backup and restore test - #342

Draft
kruchkovnik15-dot wants to merge 1 commit into
Greenstand:masterfrom
kruchkovnik15-dot:test/160-keycloak-backup-restore
Draft

kruchkovnik15-dot wants to merge 1 commit into
Greenstand:masterfrom
kruchkovnik15-dot:test/160-keycloak-backup-restore

Conversation

@kruchkovnik15-dot

Copy link
Copy Markdown

Related to #160.

Adds a reproducible local backup and restore guide and links it from the Keycloak README.

The procedure backs up the PostgreSQL keycloak schema and restores it into a separate, fresh PostgreSQL container. It documents role creation, restore ownership, verification, cleanup, and limitations before adapting it to Greenstand environments.

Validation

Manually tested with official Keycloak 23.0.0 and PostgreSQL 14 in Docker:

  • Source user login succeeded.
  • Schema backup completed.
  • Restore completed with exit code 0.
  • A separate Keycloak instance started against the restored database without administrator bootstrap variables.
  • Fresh user login succeeded with the password set before backup.
  • Administrator login succeeded; the restored realm and user were visible.
  • User ID, username, email, realm, and password-record count matched between source and restored databases.

git diff --check passed.

No Greenstand credentials, clusters, or databases were accessed or changed. The backup archive is not included in the PR.

This documents a successful local test. Recovery of Greenstand’s deployed environments, custom image, permissions, and external integrations remains unverified.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant