Skip to content
This repository has been archived by the owner on Sep 19, 2021. It is now read-only.

Separate database migration process from application runtime #119

Closed
ryanhofdotgov opened this issue May 14, 2018 · 0 comments
Closed

Separate database migration process from application runtime #119

ryanhofdotgov opened this issue May 14, 2018 · 0 comments

Comments

@ryanhofdotgov
Copy link
Contributor

Backend api process will automatically execute SQL in files in the migrations directory, depending on the value of DB_MIGRATION_TARGET and the skip-migration command-line parameter.

Improve privilege separation by:

  • moving migration code into separate tool
  • reduce privileges of PostgreSQL account used by backend api executable so as not to have any DDL modification permissions.

Mitigated by container deployment environment (container access restrictions, file system permissions, etc.) where write access to migrations implies ability to affect the entire backend.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant