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

FR: Dynamic link-call target #44

Open
Steve-Mcl opened this issue Sep 4, 2023 · 6 comments
Open

FR: Dynamic link-call target #44

Steve-Mcl opened this issue Sep 4, 2023 · 6 comments
Labels
customer request requested by customer feature-request New feature or request that needs to be turned into Epic/Story details size:S - 2 Sizing estimation point
Milestone

Comments

@Steve-Mcl
Copy link
Contributor

Description

As a user of FlowFuse I wish to perform a link-call to a targeted instance that is determined at runtime.

Similar to how the regular link-call does:

image

I realise this can be already be achieved by comparing a msg property on the project in side and decide to NOT action it, but, in order to prevent eavesdropping, my requirement is to not send the sensitive data to any instance other than the intended target.

@Steve-Mcl Steve-Mcl 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 labels Sep 4, 2023
@Steve-Mcl Steve-Mcl changed the title Dynamic link-call target FR: Dynamic link-call target Sep 4, 2023
@Steve-Mcl Steve-Mcl added the customer request requested by customer label Sep 4, 2023
@Steve-Mcl Steve-Mcl added the size:S - 2 Sizing estimation point label Sep 4, 2023
@Steve-Mcl
Copy link
Contributor Author

@robmarcer robmarcer removed the customer request requested by customer label Sep 4, 2023
@robmarcer
Copy link

This would be very useful, I'm trying to route payloads to various different devices dynamically. The only current solution (I can think of) is to send all payloads to all devices then filter out all the payloads I don't need on the device side.

@robmarcer robmarcer added the customer request requested by customer label Sep 14, 2024
@robmarcer
Copy link

Customer who would benefit from this - https://app-eu1.hubspot.com/contacts/26586079/record/0-2/8845845707

@joepavitt joepavitt moved this from Next to Scheduled in ☁️ Product Planning Sep 25, 2024
@joepavitt joepavitt removed the needs-triage Needs looking at to decide what to do label Sep 25, 2024
@joepavitt joepavitt added this to the 2.10 milestone Sep 25, 2024
@Steve-Mcl
Copy link
Contributor Author

This would be very useful, I'm trying to route payloads to various different devices dynamically.

This would depend on #30 / #91 being implemented first

@knolleary knolleary modified the milestones: 2.10, 1.10, 2.11 Oct 25, 2024
@robmarcer
Copy link

Just sharing continued appetite for this feature.

I'm at a point with a project where the lack of this feature is probably going to mean I need to drop the Project Link nodes it favour of a standard MQTT broker (possibly ours when it's available).

I have 3 environments, dev, stage, and prod. Each has a central config NR instance which then commands worker NR instance running on devices at manufacturing facilities as to what jobs they need to complete. The config payloads are sent out the to workers via the Project Link nodes. I need to be able to dynamically change the topics which the config payloads are published to ensure separation of the config between the three environments.

I appreciate that we are working towards allowing direct communication with our broker so I'm going to read up on the proposed features of that. It might be I have to stop using the Project Link nodes which is a shame as they are otherwise very useful.

@Steve-Mcl
Copy link
Contributor Author

@robmarcer this is kinda blocked waiting a reply here: #30 (comment)

@joepavitt joepavitt modified the milestones: 2.11, 2.12 Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer request requested by customer feature-request New feature or request that needs to be turned into Epic/Story details size:S - 2 Sizing estimation point
Projects
Status: Scheduled
Status: Todo
Development

No branches or pull requests

4 participants