Support separate datastore URIs for migrations and application #397
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds support for separate database connection strings for migrations versus normal SpiceDB operation.
Fixes #338
Motivation
Database migrations require elevated privileges (CREATE TABLE, DROP TABLE, ALTER TABLE) that the SpiceDB application shouldn't have during normal operation. This follows security best practices by allowing least-privilege credentials for the application.
Changes
migration_datastore_urisecret key supportmigration_datastore_uriinstead ofdatastore_uridatastore_uriexamples/separate-migration-datastore-uri/Usage