Custom "DeployTo<EnvironmentType>.ps1" not triggering

[cegekaJG]

I want to create a custom deployment process for an OnPrem environment using a PowerShell script, but it's not being executed during the CI/CD workflow.
I have the following:

• A repository with AL Go 4.0 and 2 PTE applications
• A repository environment called Docker
• .github\AL-Go-Settings.json with the following parameters:

{
  "DeployToDocker":
  {
    "runs-on": "self-hosted",
    "environmentName": "bcserver",
    "environmentType": "OnPrem"
  },
  "doNotPublishApps": true,
  "enableCodeCop": true,
  "enablePerTenantExtensionCop": false,
  "enableUICop": true,
  "githubRunner": "ubuntu-latest",
  "runs-on": "ubuntu-latest",
  "skipUpgrade": true,
  "type": "PTE",
  "useCompilerFolder": true
}

• A script called .github\DeployToOnPrem.ps1 that just prints the parameters given
• A self-hosted GitHub runner with the label self-hosted

From what I can tell, the environment settings gets read successfully and the self-hosted runner executes the job as requested; but the Deploy step is performed by microsoft/AL-Go-Actions/Deploy@v4.0, and not DeployToOnPrem.ps1. The custom script is supposed to fire at this point, correct?

[freddydk]

The custom script will be invoked inside Deploy@v4.0 - here:

AL-Go/Actions/Deploy/Deploy.ps1

Line 151 in 70ee72a

$customScript = Join-Path $ENV:GITHUB_WORKSPACE ".github/DeployTo$($deploymentSettings.EnvironmentType).ps1"

Note that the script name is case sensitive under Linux - not on Windows.

[cegekaJG]

Ah, in my case the environment was missing the AUTHCONTEXT secret, because the test didn't require one. Adding it made everything run correctly.

[curateideas]

@cegekaJG : What did you enter in the AUTHCONTEXT secret? Seems it tries to connect to a SaaS Environment anyway, despite it's set to "OnPrem"...

[cegekaJG]

I think I just entered {}. I didn't write it down and I can't see the secret value anymore.

[curateideas]

Ok, thanks!