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.

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

Updating multiple instances #3841

Open
zackwasli opened this issue May 8, 2024 · 4 comments
Open

Updating multiple instances #3841

zackwasli opened this issue May 8, 2024 · 4 comments
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do sales request requested by a sales lead

Comments

@zackwasli
Copy link
Contributor

Description

Currently you can update the image of Node-Red, but it would helpful to be able to update the code/flow also.

So, if there are multiple instance of Node-Red using the same template code/nodes, you could update them all.

Requested by:

https://app-eu1.hubspot.com/contacts/26586079/record/0-2/10189549510

Which customers would this be available to

Team + Enterprise Tiers (EE)

Have you provided an initial effort estimate for this issue?

I can not provide an initial effort estimate

@zackwasli zackwasli added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do sales request requested by a sales lead labels May 8, 2024
@knolleary
Copy link
Member

My initial interpretation of this request suggests a suitable response would be to add support for a Pipeline to deploy to multiple instances in a single stage.

But that may be misunderstanding of the request. I think we need to dig into this a bit more to understand the scenario as it can be interpreted in a few different ways - and thus satisfied in different ways. We would want to make sure we're addressing the true customer need with anything we did in response.

@zackwasli
Copy link
Contributor Author

Agreed, working to get more info on the specifics, asking these questions and will post answers: https://flowforgeworkspace.slack.com/archives/C03FAUBPPJ7/p1715202997759439?thread_ts=1715004346.071099&cid=C03FAUBPPJ7

@joepavitt
Copy link
Contributor

joepavitt commented May 22, 2024

This could read similar to #3230 where we have a centralised "store" of some Node-RED code, and that needs to be updated automatically to many instances using that code/subflow. #3841 is larger, as it could also encompass node-red versions, etc.

The other way of interpreting this is that we are being asked for "groups" of instances, similar to how we have groups of devices, and the request is simply that they want to push a single flow out to multiple FF-Hosted instances in one click. Not sure there is value in this though, as they'll all be running identical flows. With Device Groups, each device will have it's own sensors, env vars, etc. that would cause a difference in operation and data supplied.

@zackwasli
Copy link
Contributor Author

I would guess the latter, but I asked them these questions:

https://flowforgeworkspace.slack.com/archives/C03FAUBPPJ7/p1715202997759439?thread_ts=1715004346.071099&cid=C03FAUBPPJ7

on May 8th and have not gotten a reply yet. Will follow up today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do sales request requested by a sales lead
Projects
Status: 💬 Support cases & under review
Development

No branches or pull requests

3 participants