Skip to content

Add dynamic configuration management with CONFIGURE/RESET control signals#105

Draft
GaijinKa wants to merge 4 commits intomeetecho:mainfrom
GaijinKa:feature/control-payload-configure
Draft

Add dynamic configuration management with CONFIGURE/RESET control signals#105
GaijinKa wants to merge 4 commits intomeetecho:mainfrom
GaijinKa:feature/control-payload-configure

Conversation

@GaijinKa
Copy link
Member

@GaijinKa GaijinKa commented Feb 3, 2026

Description

This PR introduces configuration management capabilities to the control payload system by adding two new control signals: CONFIGURE and RESET. These signals enable dynamic runtime configuration updates for nodes without requiring a full restart.

The implementation allows nodes to receive configuration updates through the control payload mechanism, making the system more flexible and responsive to configuration changes during execution.

PR type
Select all the labels that apply to this PR.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Code refactoring
  • Performance improvement
  • Test update
  • Build/CI configuration change
  • Other (please describe):

Key modifications and changes

  • Add CONFIGURE and RESET variants to ControlSignal enum
  • Extend ControlPayload with a data dictionary field to carry configuration parameters
  • Implement update_config and reset_config method signatures in _node.py
  • Add control signal handling logic in _node.py for CONFIGURE and RESET signals
  • Update remote service to generate CONFIGURE signals on incoming configuration management requests
  • Enhance passthrough identity node to properly propagate configuration updates
  • Fix proto deserialization utilities in warp to support the new configuration data structure

Affected components

  • Juturna core library: _node.py, control payload system
  • Remote service: configuration request handling
  • Warp: proto deserialization utilities
  • Built-in nodes: passthrough identity node

Additional context

This change maintains backward compatibility as the data dictionary in ControlPayload is optional and defaults to an empty dictionary when not provided. Existing nodes that don't implement configuration updates will continue to work normally, ignoring CONFIGURE and RESET signals.

- _node.py now handles the new CONFIGURE and RESET ControlSignals
- _node.py now has both the update_config and the reset_config
  signatures
- add a data dictionary to ControlPayload
- generate a new CONFIGURE signal in remote service on incoming requests
  to manage the configuration attribute
- update passthrough identity node to handle the configuration update
  properly
@GaijinKa GaijinKa added type:enhancement New feature or request priority:medium labels Feb 3, 2026
@GaijinKa GaijinKa marked this pull request as draft February 20, 2026 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant