Importing custom rapidstart packages into container

[nikolajovicic]

I tied to use ALOpsPackageImport@1 task, but got an error: ##[error]There is no AllObj within the filter. Filters: Object Type: Page, Object ID: 8615 for which I find an explanation here: https://github.com/HodorNV/ALOps/issues/137 As I understood, it step is currently unusable, because one Microsoft's function doesn't work.

Before we switched to ALOps, we used to upload configuration packages with BcContainerHelper function UploadImportAndApply-ConfigPackageInBcContainer, so I tried to import package with PowerShell task

- task: PowerShell@2 displayName: "Import Config Package" inputs: targetType: 'inline' script: | $credential = New-Object pscredential $(ALOPS_DOCKER_ADMINUSER), (ConvertTo-SecureString -String $(ALOPS_DOCKER_ADMINPASSWORD) -AsPlainText -Force) UploadImportAndApply-ConfigPackageInBcContainer -containerName $(ALOPS_DOCKER_HOSTNAME) -configPackage "C:\ConfigurationPackages\PAYROLL-1.rapidstart" -credential $credential `

But here I got an error:

for which I also found an explanation here: https://github.com/HodorNV/ALOps/issues/293

In the end, my question is are there any possibility to import config package during pipeline run. If it is not possible, I would ask for reimplementation of this feature to be able to import packages, because problem with cmdlet New-NAVWebService is obviously unresolved since 2020, and who knows when or it will be.

[waldo1001]

We'll look into it, but need to handle other issues first.

[fvet]

@waldo1001 Any update on the status of this issue?

[CarloAxians]

Hi @waldo1001, We have the same issue. When we run the UploadImportAndApply-ConfigPackageInBcContainer command locally it's working fine, but in DevOps we get an error: The property 'Mounts' cannot be found on this object. Verify that the property exists.

[waldo1001]

The "Mounts" used by BCCH give stability issues on build agents.

But we will do 2 things.

1. We'll make it a setting to add the BCCH-mounts to the container if you'd like that.
2. A new build-step is in the roadmap to upload data configpackages.

[CarloAxians]

@waldo1001 is there an estimate when this will be delivered?

[CarloAxians]

Hi @waldo1001 , any update on this, we really need this one.

[CarloAxians]

Hi @waldo1001, still no update?

[waldo1001]

Hi @waldo1001, still no update?

It's next on the todo list. First we need to finish running BCPT from ALOps.

[nikolajovicic]

Hi @waldo1001 , can you provide approximately time when we can expect it to be finished?

[CarloAxians]

Hi @waldo1001, is there any news when this will be released?

[nikolajovicic]

Hi, did you do something about this? I didn't find any post but tried again PS script task with UploadImportAndApply-ConfigPackageInBcContainer and it worked.

Of course, it's great if you have done this, and thank you! :)

- task: PowerShell@2
  displayName: "Import Config Packages"
  inputs:
    targetType: 'inline'
    script: |
      $credential = New-Object pscredential $(ALOPS_DOCKER_ADMINUSER), (ConvertTo-SecureString -String $(ALOPS_DOCKER_ADMINPASSWORD) -AsPlainText -Force)
      UploadImportAndApply-ConfigPackageInBcContainer -containerName $(ALOPS_DOCKER_HOSTNAME) -configPackage "C:\ConfigurationPackages\PackageCURRENCIES.rapidstart" -credential $credential

Result (works):