Cloning mechanism for staging -> dev #1837
Labels
🤖 aspect: dx
Concerns developers' experience with the codebase
🌟 goal: addition
Addition of new feature
🟩 priority: low
Low priority and doesn't need to be rushed
🧱 stack: catalog
Related to the catalog and Airflow DAGs
Description
It would be ideal to have an easy way to replicate, copy, or clone our future staging database to our local dev database for easier bootstrapping of live data. This would reduce the time it would take to populate a local database and allow it to be jettisoned more easily.
Alternatives
We could potentially point dev instances directly at staging.
Additional context
Implementation
The text was updated successfully, but these errors were encountered: