Closed rdebath closed 1 year ago
Yeah, we know - they broke the External Deployer.
We're working on it!
Dear @rdebath ,
Could you please check the latest version of "ALOps.ExternalDeployer". We some major changes to the way it works. From v1.45 the ExternalDeployer is compatibel with BC v21.
Install-Module -Name ALOps.ExternalDeployer -Force
Kind regards,
Looking good, it's doing the job.
Tiny issue in that it needs an error message if the service name isn't found on service removal.
PS C:\NAV\21.0.46384\NST> Remove-ALOpsExternalDeployer -ServiceName ALOpsExternalDeployer$BCNext
PS C:\NAV\21.0.46384\NST> Remove-ALOpsExternalDeployer -ServiceName 'ALOpsExternalDeployer$BCNext'
*** Stopping existing service
*** Uninstall existing service
Name : ALOpsExternalDeployer$BCNext
DisplayName : ALOps External Deployer - BCNext
State : Stopped
PathName : C:\Program Files\ALOps\ExternalDeployer\BCNext\ALOpsExternalDeployer.exe
[SC] DeleteService SUCCESS
Describe the bug Microsoft are rejecting the Config key "LocalServiceApiKey" set by
New-ALOpsExternalDeployer
NAV Version : 21.0.46384.46844I guess you're going to have to put everything in the URL. :-|
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior No error message like earlier versions.