Hi Yash,
You're absolutely right, AL-Go for GitHub supports automatic deployment of .app files to BC SaaS environments, but it requires a few key configuration steps to activate.
Here’s what to check:
- By default, AL-Go generates the .app file and stores it in GitHub artifacts, but deployment only occurs if a target environment is registered and the correct secrets are configured.
- To enable automatic deployment:
- Define your environment in
.github/AL-Go-Settings.json using "EnvironmentType": "SaaS"
- Add an
authContext secret for that environment in GitHub (or Azure Key Vault)
- This includes
clientId, clientSecret, tenantId, and optionally environmentName
- Ensure the environment name matches what’s defined in your BC Admin Center
- You can also override the default deployment behavior by creating a custom script like
DeployToSaaS.ps1 in the .github folder. This gives you full control over how and when deployment occurs.
- Once configured, AL-Go will automatically deploy the .app file to the specified SaaS environment after a successful build, unless gated by a manual release or approval step.
Helpful references:
Overview of AL-Go – Microsoft Docs
Settings and Deployment Scenarios – Freddy Kristiansen
Getting Started with AL-Go – DeepWiki
Do-it-yourself CI/CD with AL-Go – Yzhums PDF
AL-Go GitHub Repository – Microsoft
If you find this helpful, feel free to mark this as the suggested or verified answer.
Cheers
Jeffrey
