Skip to content

UpdateAlGoSystemFiles.md

Latest commit

 

History

History
29 lines (15 loc) · 2.32 KB

UpdateAlGoSystemFiles.md

File metadata and controls

29 lines (15 loc) · 2.32 KB

Update AL-Go system files

Prerequisites: A completed "Register a customer production environment for Manual Deployment" scenario and a GhTokenWorkflow secret, created following this walkthrough

  1. Every time a CI/CD pipeline runs, it checks whether there are updates to AL-Go system files. AL-Go System files are scripts in the .AL-Go folder plus scripts and workflows in the .github folder. Looking at the latest CI/CD workflow, we can see that updates are available.

    Updates available

  2. In VS Code, try to modify the LocalDevEnv.ps1 file, stage the change, commit and push.

    localdevenv

  3. Now there is an additional difference. AL-Go doesn’t support that anybody changes the AL-Go system files and will warn about these changes. The CI/CD pipeline, which kicked off when pushing the change, tells me about this.

  4. To update the AL-Go system files using the Update AL-Go System Files workflow, you need to provide a secret called GHTOKENWORKFLOW (see prerequisites). If not already done, please use this walkthrough to create this secret.

  5. On github.com, under Actions in your project, select the Update AL-Go system files workflow and choose Run workflow. Leave the Template Repository URL blank and choose Run workflow.

    Update AL-Go System Files

  6. Inspect the pull request and see that it indeed reverts your change to the LocalDevEnv.ps1 file and removes the PowerPlatform functionality, since we do not have any PowerPlatform apps included.

    Inspect

  7. By default, this workflow will apply any updates to the workflow files (in .github\workflows) or system scripts (in .AL-Go) from the template repository used to spin up the repository. If you want to change branch or template Url, you can specify the templateUrl@branch when you run the workflow.

back