Moving app from Dev to Prod with seperate SharePoint and Flow connections

[Fox]

So as per the title, I currently have a 1 which i've then copied and called one Prod and one Dev. They both live in the same PowerApps Environment (Default one whcih comes with office 365)

In order to maintain proper version control and a proper release management strategy, i've also gone and copied the data base (SharePoint) and Flows. My question is what is the easiest way to move apps from Dev to Prod?

Example:

App1 Prod

- Connects to and Stores data on SharePoint site: https://mytenant.sharepoint.com/sites/prod/somelist

- Uses a Flow called App1 Prod Flow to send some emails

App 1 Dev

- Connects to and Stores data on SharePoint site: https://mytenant.sharepoint.com/sites/dev/somelist

- Uses a Flow called App1 Dev Flow to send some emails

I know I can use the Package app feature but that won't update the data connections to the correct SharePoint and flow environments. 

Example, If I exported App 1 Dev and imported it back in, it would still hold on to the incorrect Data Source for SharePoint? 

Any guidance

[Mickyw]

Just sharing my experience on this as I do similar thing but I also wish there was better way:

• I do have a subsite with same sharepoint lists as in main site - subsite is called "sandbox". 
• During refresh I backup production version of application, then remove it and save Development one as Production
• I edit Production just to delete all sources from "sandbox" subsite and add sources from main Sharpoint URL. I do however share Flow between these two. Otherwise I think you need to rename all the calls to Flow within your application too
• I use one trick thow, which helps me a little. During OnStart I check to which Sharepoint one of my lists is connected (I do this by looking into first row and one of its columns - somthing with "link" in the name - I do use Polish locales so I don't know original name for this). I set global variable onProd to true if not on sandbox - which I later use to change the name of application and some colors, etc. So I do know on which data source application is running.
• I've also created simple helper app - which copies data from lists on Production to Development (sandbox). It also helps to test and repair the code.

I agree that should be much easier. For example this PowerApps Idea might be useful if it would handle custom metadata properties. But still I think that PowerApps - due to its strict syntax control - will not allow dynamic (i.e. programatically changed) change in data source or Flow name, etc. 

Regards,

Mick