dohertj2/wwtools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mxaccesscli: route write through Advise vs AdviseSupervisory by user

Browse Source 
WriteCommand now picks the LMXProxyServer advise variant based on
whether credentials were supplied:

  --username given  -> Advise            (operator action; the write
                                          is attributed to the
                                          authenticated Galaxy user
                                          in the alarm/event audit
                                          trail)
  no --username     -> AdviseSupervisory (supervisory action; the
                                          write is attributed to the
                                          hosting client itself, no
                                          Galaxy user claimed)

MxItem grows AdviseSupervisory() alongside Advise() and shares the
same UnAdvise / RemoveItem teardown.

Verified live with the trigger / ack-as-dohertj2 / clear sequence on
TestMachine_001.TestAlarm002. The Set (anonymous, supervisory) and
Clear (anonymous, supervisory) rows pair with the Acknowledged row
(authenticated, Advise) under one Alarm_ID. On this development
galaxy every action still maps to User_Name=DefaultUser regardless
of advise variant — that's a galaxy-security configuration trait,
not a CLI bug. The routing is in place and will differentiate
correctly on a strict galaxy with real user records.

docs/usage.md gains an "Advise variant" section explaining the rule
and the expected User_Name population on strict vs permissive
galaxies.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Joseph Doherty
2026-05-03 22:10:25 -04:00
parent 0d25ec445f
commit 9de8660688
3 changed files with 39 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mxaccesscli/src/MxAccess.Cli/Mx/MxItem.cs
+12
View File
@@ -32,6 +32,18 @@ namespace MxAccess.Cli.Mx
_advised = true;
}
/// Subscribe in supervisory mode. Use this for actions that should
/// be attributed to the hosting client (rather than to a Galaxy user)
/// in the alarm/event audit trail — e.g. anonymous bulk operators,
/// integration scripts, or automation acting on its own authority.
/// Pairs with the same UnAdvise / RemoveItem teardown as Advise().
public void AdviseSupervisory()
{
if (_advised) return;
_proxy.AdviseSupervisory(_hServer, Handle);
_advised = true;
}
public void UnAdvise()
{
if (!_advised) return;