Skip to content

Support hot-reloadable Elephant Agent configuration #7

Description

@Xunzhuo

Goal

Support hot-reloadable Elephant Agent configuration so selected settings can change without a full restart.

Scope

  • Config ownership and reload boundaries
  • Which settings are hot-reloadable vs restart-required
  • Watch/reload mechanism and validation flow
  • Runtime notification to affected subsystems
  • User-facing diagnostics for rejected config updates

Acceptance Criteria

  • A config reload policy distinguishes hot-reloadable and restart-required fields.
  • Config changes are validated before they affect live runtime state.
  • At least one representative setting can be changed and observed without restart.
  • Invalid updates fail closed with actionable diagnostics.
  • Tests cover valid reload, invalid reload, and no-op reload behavior.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/configConfiguration and runtime settingsarea/operatorOperator actions and self-managementarea/runtimeRuntime orchestration and local executionenhancementNew feature or requestkind/featureProduct or platform capability requestpriority/p1High priority roadmap work

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions