Currently CI and Production are immediately impacted by database modifications, making them unstable whenever development affects how data is stored.
Bug Aspect:
ex. Global search currently isn't working because of a change in how "Alternate Titles" for movies are being stored in the database.
Desired outcome - Have production (probably not CI) pull from a different database (ideally through convention - aka not manually changing code before pushing to production) local environments.
Likely Tasks
Create another firebase instance for non-production environments.
Spike on how to configure the build process to inject different firebase connection data depending on target environment.
Implement solution that, at a minimum, resolves the issue of active development destabilizing production.
Problem description
Currently CI and Production are immediately impacted by database modifications, making them unstable whenever development affects how data is stored.
Bug Aspect:
ex. Global search currently isn't working because of a change in how "Alternate Titles" for movies are being stored in the database.
Desired outcome - Have production (probably not CI) pull from a different database (ideally through convention - aka not manually changing code before pushing to production) local environments.
Likely Tasks