feat(BA-435): Implement GQL for querying and modifying AbusingReportConfig

[jopemachine]

Aims to resolve #3342 (BA-435).

How it works

In the case of configuration change mutations, only specific settings are modified through an RPC call named set_local_config.

The agent called via set_local_config updates its in-memory local_config and also updates the agent.toml file to ensure that the changed settings are retained even after a reboot.

Considerations

Note

Please note that settings used in initialization logic will not be applied immediately.

For example, in the case of modify_abusing_report_config, the initialization logic in AbstractAgent.__ainit__() that recursively creates the folder if the abuse-report-path does not exist will not be executed. Therefore, the directory for abuse-report-path must already exist.

Query example

query {
  abusing_report_config(agent_id: "<agent_id>") {
    abuse_report_path
    force_terminate_abusing_containers
  }
}

Mutation example

mutation {
  modify_abusing_report_config (agent_id: "<agent_id>", props: { abuse_report_path: "<abuse_report_path>" }) {
    ok
  }
}

Checklist: (if applicable)

• Milestone metadata specifying the target backport version
• Mention to the original issue
• API server-client counterparts (e.g., manager API -> client SDK)
• Test case(s) to:
  • Demonstrate the difference of before/after
  • Demonstrate the flow of abstract/conceptual models with a concrete implementation

---

📚 Documentation preview 📚: https://sorna--3355.org.readthedocs.build/en/3355/

---

📚 Documentation preview 📚: https://sorna-ko--3355.org.readthedocs.build/ko/3355/