For a blogpost, I'm creating a CloudFormation temp...
# spicedb
s
For a blogpost, I'm creating a CloudFormation template to run SpiceDB on ECS and using Postgres on Amazon RDS as a datastore. I see the following error in the logs when it's deployed: Oddly, if I follow the same steps by clicking through ECS and RDS (click-ops style i.e) it works fine.
Copy code
(UTC+1:00)
    
{"level":"error","pgx":{"args":[],"err":"ERROR: relation \"alembic_version\" does not exist (SQLSTATE 42P01)","pid":1082,"sql":"SELECT version_num from alembic_version","time":0.467843},"time":"2024-12-16T17:28:11Z","message":"Query"}
    
{"level":"warn","datastoreReady":false,"time":"2024-12-16T17:28:10Z","message":"datastore failed readiness checks: datastore is not migrated: currently at revision ``, but requires `add-metadata-to-transaction-table`. Please run `spicedb migrate`. If you have previously run `TRUNCATE`, this database is no longer valid and must be remigrated. See: https://spicedb.dev/d/truncate-unsupported"}
I can run the
spicedb migrate
command and it works fine after that, but i'd like it to work without having to run that command first. Any idea why this happens?
6 Views