Add control over contents of exported and imported Snapshots
Closed this issue · 4 comments
Description
We offer the feature to "Export" Snapshots, this contains, in a single file, the flows
, credentials
and environment variables
for a given Instance. Users can then import that into another Application, or instance of FlowFuse.
The challenge here is that we have customers running multiple instances of FlowFuse, where one instance is entirely development-only, and the other is production-only, and they want to be able to transfer instances between. The difficulty here is that our DevOps Pipelines are limited to instances within a single FlowFuse instance, and as such, users are having to resort to manual export/import.
The manual route works, but contains env vars from development environments, and overwrites production credentials when imported. As such, the following is required of our import/export functionality:
We already have a similar UX for the control of the contents in the "Duplicate Instance" here:
Which customers would this be available to
Everyone - CE/Starter/Team/Enterprise
Requested By:
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
Having read the support ticket (and used a bit of personal experience) I see a few of short comings in this proposal:
- We want to export all 995 env vars except the 5 "XXX_PASSWORD" env vars - these should never be exposed to the file system or included in a download!
- We want to export all 1000 env vars but leave specific keys (like "XXX_PASSWORD") empty (so it can be filled in by the recipient instance before firing it up)
- We want to import the snapshot and leave any existing ENV VARS in tact - like the pipeline does today. That permits us to prepare the new instances ahead of time and simply import the snapshot leaving the 5 "XXX_PASSWORD" fields I already setup on the new instance intact.
Given the option to simply exclude or include (keys with or without values) is not really helpful in the above situations.
I realised these may be follow up items but I wanted to explicitly call them out (slightly exaggerated) to put emphasis on the short fall I see.
Yes please
I realised these may be follow up items but I wanted to explicitly call them out (slightly exaggerated) to put emphasis on the short fall I see.
Agreed, follow up item. Let's at least give them the option to have just the flows transferred over, env vars refinement can follow