Centralised Config Nodes (Management & Distribution)
Open
epic
headline
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 146
Description
As a FlowFuse User
I want to be able to manage my configuration nodes at the team- and application-level
So that I do not have to duplicate effort in dozens of places when managing integrations with external resources and services
```[tasklist]
### Tasks
- [ ] Make available the MQTT Clients configs in Node-RED Instances
```
The Team Library here is a sensible place for this to live, but the key here is that we want to enable is the automatic availability of these config nodes within Node-RED
Consequences/side-effects here need to be considered. Flows being restarted may trigger logic in user's flows, or trigger restarts/deployment mid-editing.
Contributor guide
Assessment
This issue has not been assessed yet.