Add opportunity to store Pipelines data in the database
Problem to solve
Currently, if the project is deployed as a docker container - the user can not CRUD pipelines. Basically he's not able to do anything with the pipeline, but to start it. The cause of that issue is that containerized project is being run in read-only mode. It's possible to turn that setting off, and allow the user to work with pipelines, but all changes will not survive a server restart or container update - as these are not stored in persistent storage like DB or external file storage.
Target audience
The users of Meltano UI.
Further details
(Include use cases, benefits, and/or goals)
Proposal
To store pipeline configuration details in external DB alongside storing them in meltano.yml file, with the ones in DB taking precedence.
What does success look like, and how can we measure that?
When we deploy containerized version of Meltano, the user can make changes into pipeline configuration. If we do a server restart, or update meltano version and deploy new container - user-made changes must still be there.