You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to isolate database interaction between applications, datagov wants to create 2 instances of postgres with the flask app talking to one and harvesting logic talking to the other.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
GIVEN the flask app and harvesting logic app
WHEN a call is made from an app
THEN the associated db is used
Background
we're currently using 2 databases. postgres for the flask app and an in-memory sqlite instance for the harvesting logic app.
part of #4731 is updating the data type of the "notification_emails" column in the harvest source table to an array of strings. sqlite doesn't support arrays as column data types so we're replacing sqlite with our postgres instance. the flask app and harvesting logic app are then interacting with the same database. this poses a problem.
the harvesting logic app modifies the state of the database in its tests which interferes with the functionality of the flask app.
we want to create 2 database instances to prevent interference of applications.
User Story
In order to isolate database interaction between applications, datagov wants to create 2 instances of postgres with the flask app talking to one and harvesting logic talking to the other.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
WHEN a call is made from an app
THEN the associated db is used
Background
Security Considerations (required)
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
Sketch
--scale
flagThe text was updated successfully, but these errors were encountered: