Agent exe for windows arm64 is not included in the jar package

[vitorallo]

Description

The arm64 build of the agent is not available and the webserver returns a 500 errr.

Environment

1. OS (where OpenBAS server runs): docker container
2. OpenBAS version: image openbas/platform:1.7.3
3. OpenBAS client: windows amr64
4. Other environment details:

Reproducible Steps

http://openbas:8080/api/agent/package/openbas/windows/arm64

Expected Output

download the agent build in exe

Actual Output

Stop-Service:
Line |
5 | Stop-Service -Force -Name "OBAS Agent Service"; Invoke-WebRequest -Ur …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Cannot find any service with service name 'OBAS Agent Service'.
Invoke-WebRequest:
Line |
5 | … t Service"; Invoke-WebRequest -Uri "http://pisellolab.vitorallo.com:8 …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
{
"timestamp": "2024-10-18T15:33:19.163\u002B00:00",
"status": 500,
"error": "Internal Server Error",
"path": "/api/agent/package/openbas/windows/arm64"
}
./openbas-installer.exe:
Line |
5 | … e}" -OutFile "openbas-installer.exe"; ./openbas-installer.exe /S ~OPE …
| ~~~~~~~~~~~~~~~~~~~~~~~
| The term './openbas-installer.exe' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Remove-Item:
Line |
5 | … Y=false; Start-Sleep -Seconds 1.5; rm -force ./openbas-installer.exe;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Cannot find path 'C:\Users\me\openbas-installer.exe' because it does not exist.

Additional information

by calling the api on the browser at the address specified by the .ps1 install script, manually

Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.

Fri Oct 18 15:40:23 UTC 2024
There was an unexpected error (type=Internal Server Error, status=500).

Screenshots (optional)

[isselparra]

Hi @vitorallo,

Thank you for reporting this issue.

Currently we don't support Windows Arm64, and you are seeing this problem since the corresponding artifact it's not available.

We’re prioritizing this issue in our upcoming milestones.