Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Node-RED Version Control #3574

Closed
4 of 7 tasks
joepavitt opened this issue Mar 14, 2024 · 4 comments
Closed
4 of 7 tasks

Node-RED Version Control #3574

joepavitt opened this issue Mar 14, 2024 · 4 comments
Labels
epic A significant feature or piece of work that doesn't easily fit into a single release needs-triage Needs looking at to decide what to do

Comments

@joepavitt
Copy link
Contributor

joepavitt commented Mar 14, 2024 •
edited
Loading

Description

An area we need to improve, which should be a staple "wow"/highlight feature of FlowFuse is Node-RED Version Control.

Current Implementation

  • We currently offer "Snapshots" as a way of capturing point-in-time flows and associated settings, environment variables, etc.
  • We also offer the ability to "rollback" to any historical snapshot taken

Areas For Improvement

  • We have had multiple customers requesting git integration within FlowFuse
  • We should offer a clear picture on the history of changes made to a Node-RED Instance in FlowFuse
  • We should offer a clear "differences" view between two point in time instances of a flow

Other Information

Which customers would this be available to

Other - Open for discussion

Requested by:

Stories
Preview Give feedback
  1. Visualize Flows without opening a full Node-RED Editor #3623
    5 of 5
    size:M - 3 story
  2. Compare Snapshots #3624
    4 of 5
    customer request headline sales request size:L - 5 story
    Steve-Mcl
  3. Git Integration #3625
    0 of 1
    epic headline
    knolleary
  4. Singular View of Deployed Flows #4305
    2 of 2
    area:api area:frontend epic headline
  5. Visual Timeline of Version History #4304
    area:frontend epic headline size:XL - 8
    cstns
  6. SubFlow Version control #3666
    feature-request needs-triage
  7. Updating multiple instances #3841
    feature-request needs-triage sales request
@joepavitt joepavitt added the epic A significant feature or piece of work that doesn't easily fit into a single release label Mar 14, 2024
@joepavitt joepavitt added the needs-triage Needs looking at to decide what to do label Mar 14, 2024
@joepavitt
Copy link
Contributor Author

Capturing this as a high-level epic after some discussions with customers, and internal conversations in Product review meetings.

@joepavitt
Copy link
Contributor Author

Another example here from Slack whereby a team is manually copying an instance in order to make changes, then manually merging them into production instance.

@MarianRaphael
Copy link
Contributor

See also #2089

This was referenced Mar 25, 2024
Closed
Closed
Open
@joepavitt joepavitt moved this from Short to Next in ☁️ Product Planning May 7, 2024
@Steve-Mcl Steve-Mcl mentioned this issue Sep 16, 2024
Closed
@joepavitt
Copy link
Contributor Author

Closing as replaced by the "Area" field for the Product Planning board, this was just an admin catch-all for "Version Control" stuff

@github-project-automation github-project-automation bot moved this from Next to Closed / Done in ☁️ Product Planning Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
epic A significant feature or piece of work that doesn't easily fit into a single release needs-triage Needs looking at to decide what to do
Projects
☁️ Product Planning
Status: Closed / Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MarianRaphael @joepavitt