-
Notifications
You must be signed in to change notification settings - Fork 176
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[releases/24.x] Update AL-Go System Files from microsoft/AL-Go-PTE@pr…
…eview - e23536e3e226943446586ba1222608a2025935d7 (#1628) ## preview Note that when using the preview version of AL-Go for GitHub, we recommend you Update your AL-Go system files, as soon as possible when informed that an update is available. ### Issues - Issue 1105 Increment Version Number - repoVersion in .github/AL-Go-Settings.json is not updated - Issue 1073 Publish to AppSource - Automated validation: failure - Issue 980 Allow Scope to be PTE in continuousDeployment for PTE extensions in Sandbox (enhancement request) - Issue 1079 AppSource App deployment failes with PerTenantExtensionCop Error PTE0001 and PTE0002 - Issue 866 Accessing GitHub Environment Variables in DeployToCustom Scenarios for PowerShell Scripts - Issue 1083 SyncMode for custom deployments? - Issue 1109 Why filter deployment settings? - Fix issue with github ref when running reusable workflows - Issue 1098 Support for specifying the name of the AZURE_CREDENTIALS secret by adding a AZURE_CREDENTIALSSecretName setting - Fix placeholder syntax for git ref in PullRequestHandler.yaml ### Dependencies to PowerShell modules AL-Go for GitHub relies on specific PowerShell modules, and the minimum versions required for these modules are tracked in [Packages.json](https://raw.githubusercontent.com/microsoft/AL-Go/main/Actions/Packages.json) file. Should the installed modules on the GitHub runner not meet these minimum requirements, the necessary modules will be installed as needed. ### Support managed identities and federated credentials All authentication context secrets now supports managed identities and federated credentials. See more [here](Scenarios/secrets.md). Furthermore, you can now use https://aka.ms/algosecrets#authcontext to learn more about the formatting of that secret. ### Business Central Performance Toolkit Test Result Viewer In the summary after a Test Run, you now also have the result of performance tests. ### New Settings - `deployTo<environmentName>`: is not really new, but has a new property: - **Scope** = specifies the scope of the deployment: Dev, PTE. If not specified, AL-Go for GitHub will always use the Dev Scope for AppSource Apps, but also for PTEs when deploying to sandbox environments when impersonation (refreshtoken) is used for authentication. - **BuildMode** = specifies which buildMode to use for the deployment. Default is to use the Default buildMode. - **\<custom>** = custom properties are now supported and will be transferred to a custom deployment script in the hashtable. - `bcptThresholds` is a JSON object with properties for the default thresholds for the Business Central Performance Toolkit - **DurationWarning** - a warning is issued if the duration of a bcpt test degrades more than this percentage (default 10) - **DurationError** - an error is issued if the duration of a bcpt test degrades more than this percentage (default 25) - **NumberOfSqlStmtsWarning** - a warning is issued if the number of SQL statements from a bcpt test increases more than this percentage (default 5) - **NumberOfSqlStmtsError** - an error is issued if the number of SQL statements from a bcpt test increases more than this percentage (default 10) > \[!NOTE\] > Duration thresholds are subject to varying results depending on the performance of the agent running the tests. Number of SQL statements executed by a test is often the most reliable indicator of performance degredation. AB#420000 Co-authored-by: bcbuild-github-agent <[email protected]>
- Loading branch information
1 parent
3f912d1
commit 120c415
Showing
23 changed files
with
100 additions
and
98 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.