Trouble testing a rule in on premise Azure DevOps Server from the CLI

[vlaquest]

Hi,
Is it supported to launch the invoke command and target a local azure devops server?

The mapping works, and the logs show that the rule is working

$env:Aggregator_SharedSecret='e9x0fB54'
aggregator-cli map.local.rule --targetUrl https://mylocaltfsaggregator --rule Hello --project MyTeamProject --event workitem.updated

Also logon works (integrated auth or pat also works):
aggregator-cli logon.ado -u https://myserver/MyCollection -m integrated

However, I would like to test the rule on a single work item without deploying it, is it possible?
aggregator-cli invoke.rule --local --source .\hello.rule --dryrun -p MyTeamProject -e "workitem.updated" -w 586774

When calling invoke, I'm getting:

[2025-06-05 11:25:05Z] aggregator-cli v1.2.0 (build: 1.2.0.0 Release) (c) Copyright © TFS Aggregator Team
[2025-06-05 11:25:05Z] No cached Azure credential: run the logon.azure command.
[2025-06-05 11:25:05Z] Exiting with code 99

I guess I'm wrong with the parameters...

[vlaquest]

I manage to start the cli from my Visual Studio, debugging.
Actually, the Invoke command seems to require both authentications (Azure and DevOps)

cf RunAsync in InvokeRuleCommand.cs :
var context = await Context
.WithAzureLogon()
.WithDevOpsLogon()
.BuildAsync(cancellationToken);

Calling both WithxxxLogon will require both auth to be satisfied when running.
I removed the call to WithAzureLogin() and now, the invoke succeeds.

According to the docs, this command should work in local devops mode and not require an Azure Logon :(

[vlaquest]

Patch proposition to "repair" this.

In InvokeRuleCommand.cs, replace:

      var context = await Context
          .WithAzureLogon()
          .WithDevOpsLogon()
          .BuildAsync(cancellationToken);

with:

      var builder = Local ? Context.WithDevOpsLogon() : Context.WithAzureLogon();
      var context = await builder.BuildAsync(cancellationToken);