HodorNV / ALOps

ALOps
55 stars 24 forks source link

ALOpsAppClean@1 cannot bind parameter 'id' error #735

Closed dvanes67 closed 3 months ago

dvanes67 commented 3 months ago

Describe the bug AlOpsAppClean ends with an error. (we didn't change the yaml file)

the used yaml

          - task: ALOpsAppClean@1
            displayName: 'ALOps App Cleaner'
            inputs:
              nav_serverinstance: '$(TargetInstance)'

the output

Starting: ALOps App Cleaner
==============================================================================
Task         : ALOps App Cleaner
Description  : Remove AL Extensions from Business Central
Version      : 1.463.5216
Author       : Hodor
Help         : Remove all extensions from Business Central service tier.
==============================================================================
*** Validate configuration
*** Task Inputs:

name                                 value
----                                 -----
usedocker                            False
fixed_tag                                 
nav_computername                 localhost
nav_serverinstance   Test_Integration_test
sync_mode                              Add
includemicrosoftapps                 False

*** For documentation, please visit   : https://www.alops.be/documentation

*** ALOps License:
  * Licensed To: QwinSoft BV. (RepositoryPer5 License)

*** Importing required PS-Functions
*** Load module [Microsoft.Dynamics.Nav.Management]
*** Load module [Microsoft.Dynamics.Nav.Apps.Management]
##[error]Cannot bind parameter 'Id'. Cannot convert value "[Guid]::Parse" to type "System.Guid". Error: "Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)."
Finishing: ALOps App Cleaner

Expected behavior I expect it to do what it did yesterday. remove all the apps (except those installed by microsoft

Additional context We run this on-prem, but it always worked fine. it is our nightly test run, and as much as I like to see that no test have failed. I'd prefer it if they actually ran.

sorenkgmi commented 3 months ago

We got the same for customers doing deployment releases tonight.

dvanes67 commented 3 months ago

And just like that, the pipelines worked again last night. As far as I'm concerned, this issue can be closed

waldo1001 commented 3 months ago

We did a hotfix yesterday ;-)