AL-Go for Github June Office Hour
AL-Go for GitHub June office hour: features previewed last month have now shipped in version 7.2. Three new preview features are expected in 7.3: a starter Azure Data Explorer dashboard for AL-Go telemetry, custom template repositories and custom jobs. The session also warns that AL-Go versions lower than 5.0 will break very soon.
- Introduction and Agenda
- Version 7.2 Features Released
- Preview Feature 1: Starter Dashboard for AL-Go Telemetry
- Preview Feature 2: Custom Template Repositories
- Preview Feature 3: Custom Jobs
- Version Deprecation Announcement
- Q&A and Closing
Overview
The session covers AL-Go for GitHub version 7.2, which contains features that were previously in preview. It then walks through three features that are in preview and not part of 7.2, with the speakers saying they will be available in 7.3.
The preview features are a starter Azure Data Explorer dashboard for AL-Go telemetry, custom template repositories, and custom jobs in AL-Go workflows. All three were demoed. The session ends with a notice that AL-Go versions lower than 5.0 will break very soon, followed by Q&A.
Key points
- AL-Go 7.2 has shipped and includes the features that were in preview last month. See the AL-Go release notes for details.
- The starter telemetry dashboard is in preview. It is a plug-and-play Azure Data Explorer report that connects to Application Insights and shows running workflows, failures, minutes on GitHub-hosted versus self-hosted runners, AL-Go versions per repo and deprecated settings. You download a JSON file from the AL-Go repository and fill in a couple of things.
- Custom template repositories are in preview. You can put your own template repository between AL-Go PTE or AppSource and your repos, so custom scripts and workflows propagate when you run update AL-Go system files.
- Custom jobs are in preview. You add them to the AL-Go workflow YAML files by prefixing the job name with custom-job-.
- Use custom jobs carefully. AL-Go may rename jobs or change its YAML files and break customizations, so review the changes whenever you update system files.
- The three preview features are not in 7.2 but are expected in 7.3. To use them now, upgrade to preview.
- If you run an AL-Go version lower than 5.0, upgrade, because it will break very soon.
Features
| Feature | Status | At | Evidence |
|---|---|---|---|
| AL-Go Version 7.2 | status not stated | 0:37 | |
| Starter Dashboard for AL-Go Telemetry | preview, demoed | 1:36 | “they’re all in preview. Uh so yeah, not available in 7.2. Uh but they will be available in 7.3 when we release that.” (1:22) |
| Custom Template Repositories | preview, demoed | 3:54 | “They’re all in preview, like I said, so you won’t be able to find them in version 7.2.” (7:06) |
| Custom Jobs in AL-Go Workflows | preview, demoed | 5:45 | “They’re all in preview, like I said, so you won’t be able to find them in version 7.2.” (7:06) |
| AL-Go Version 5.0 End of Support | status not stated | 7:20 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
Quotes
- 0:53 “we’ve shipped it as part of version 7.2”
- 1:22 “they’re all in preview. Uh so yeah, not available in 7.2. Uh but they will be available in 7.3”
- 1:56 “It’s pretty much like a plug-and-play Azure Azure data explorer uh report.”
- 4:47 “with custom templates you can basically stick your own template repository in the middle”
- 6:01 “you can add your own custom jobs to these workflows as long as you you prefix it with custom job dash”
- 6:27 “we don’t really make any we can’t really make any promises that we won’t change the name of one of our jobs”
- 7:20 “if you are running an ALGO version lower than 5.0, then please upgrade because this will break very soon”
Disclaimers in the video
- 1:22 preview: they’re all in preview. Uh so yeah, not available in 7.2. Uh but they will be available in 7.3 when we release that.
- 6:27 subject-to-change: we don’t really make any we can’t really make any promises that we won’t change the name of one of our jobs or something like that
- 6:39 subject-to-change: we may make changes to our YAML files that will break some of your customizations that you build on top of it
- 7:20 coming-later: if you are running an ALGO version lower than 5.0, then please upgrade because this will break very soon
Presenters (as heard): Alexander, Sebastian.
