Skip to content

Conversation

@SaikiranSurapalli17
Copy link
Contributor

@SaikiranSurapalli17 SaikiranSurapalli17 commented Jun 6, 2025

SpiceDB Database Schema Failures: Missing Core Tables

Detects high-severity failures in SpiceDB when critical PostgreSQL migration tables
(e.g., alembic_version, metadata, relation_tuple_transaction) are missing
or inaccessible. These failures lead to complete authorization service disruption.

This rule helps catch issues such as:

  • Missing or skipped database migrations
  • Corrupt or incomplete datastore initialization
  • Unexpected datastore schema changes

/claim #60
/close #60

Updated categories and tags

Reproduction Steps:

chmod +x reproduce_spicedb_crash.sh

./reproduce_spicedb_crash.sh
       
tail -f test.log

Reproducible test setup (Maintainers invited): cre-spicedb

Live CRE Detection: CRE Playground

@SaikiranSurapalli17
Copy link
Contributor Author

demo.mp4

@tonymeehan tonymeehan self-requested a review June 7, 2025 05:09
@tonymeehan tonymeehan merged commit 967fd54 into prequel-dev:main Jun 7, 2025
2 checks passed
@SaikiranSurapalli17 SaikiranSurapalli17 deleted the cre-spicedb branch June 7, 2025 06:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[New Rule] SpiceDB: Reproduce A High-Severity Failure & Write a Detection Rule

3 participants