FlowFuse / FlowFuse/flowfuse

Merging multiple instances in staged deployments

Open
#1,977 0 comments 0 reactions 0 assignees View on GitHub
needs-triage type:feature
Dominant language
JavaScript
Stars
400
Forks
89
Avg merge
1d 20h
Merged PRs (30d)
149

Description

### Description

Related #1492

A couple customer conversations have asked about the ability to selectively merge flows from different instances when deploying to a production instance.

# Scenario 1

- Instance A: contains common flows that are required to be included in all production deploys
- Instance B: contains a specific set of application flows

Requirement is to deploy to Instance C (aka production) the combined set of flows from both A and B

# Scenario 2

A Team is developing multiple applications - each in its own instance. However the flows are very low-traffic and would be inefficient to have a 'production' instance for each one. A more effective solution would be to group instances together when deploying to individual production instances.

# Scenario 3

Extending scenario 1, to be able to select individual tabs (flows) from an instance when combining.

---

This would require a UX that supports many-to-1 mappings in the pipeline - not the 1-to-1 mapping currently envisaged.

## Customer Interest
- https://app-eu1.hubspot.com/contacts/26586079/record/0-2/7023192789

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.