You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Script for creating cloud development environment
3
-
# Please do not modify this script as it will be auto-updated from the AL-Go Template
4
-
# Recommended approach is to use as is or add a script (freddyk-devenv.ps1), which calls this script with the user specific parameters
5
-
#
1
+
<#
2
+
.SYNOPSIS
3
+
Creates a cloud-based development environment for Business Central AL development using SaaS Sandbox.
4
+
5
+
.DESCRIPTION
6
+
This script sets up a cloud-based development environment by:
7
+
- Creating a Business Central SaaS Sandbox environment
8
+
- Compiling and publishing all apps and test apps to the development scope
9
+
- Configuring launch.json for Visual Studio Code with Cloud Sandbox configuration
10
+
- Optionally applying custom settings to override repository settings
11
+
12
+
The script will prompt you interactively for authentication using device code flow.
13
+
For automated/unattended execution, you can configure AdminCenterApiCredentials as a GitHub secret
14
+
or in Azure KeyVault. See https://aka.ms/algosettings for more information about AdminCenterApiCredentials.
15
+
16
+
This is an alternative to localDevEnv.ps1 for users who cannot run Docker containers locally.
17
+
18
+
RECOMMENDED USAGE:
19
+
Instead of modifying this script directly (which will be overwritten during AL-Go updates),
20
+
create a custom script that calls this one with your preferred parameters. For example,
21
+
create a file named after yourself (e.g., 'john-devenv.ps1') that contains:
22
+
23
+
# My personal cloud development environment script
Copy file name to clipboardExpand all lines: .github/RELEASENOTES.copy.md
+65-1Lines changed: 65 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,67 @@
1
+
## v8.1
2
+
3
+
### Custom AL-Go files
4
+
5
+
AL-Go for GitHub now supports updating files from your custom templates via the new `customALGoFiles` setting. Read more at [customALGoFiles](https://aka.ms/algosettings#customALGoFiles).
6
+
7
+
### Set default values for workflow inputs
8
+
9
+
A new setting `workflowDefaultInputs` allows you to configure default values for workflow_dispatch inputs. This makes it easier to run workflows manually with consistent settings across your team.
10
+
11
+
When you add this setting to your AL-Go settings file and run the "Update AL-Go System Files" workflow, the default values will be automatically applied to the workflow YAML files in your repository.
12
+
The default values must match the input types (boolean, number, string, or choice) defined in the workflow YAML files.
13
+
14
+
Example configuration:
15
+
16
+
```json
17
+
{
18
+
"workflowDefaultInputs": [
19
+
{ "name": "directCommit", "value": true },
20
+
{ "name": "useGhTokenWorkflow", "value": true }
21
+
]
22
+
}
23
+
```
24
+
25
+
This setting can be used on its own in repository settings to apply defaults to all workflows with matching input names. Alternatively, you can use it within [conditional settings](https://aka.ms/algosettings#conditional-settings) to apply defaults only to specific workflows, branches, or other conditions.
26
+
27
+
Example using conditional settings to target specific workflows:
28
+
29
+
```json
30
+
{
31
+
"conditionalSettings": [
32
+
{
33
+
"workflows": ["Create Release"],
34
+
"settings": {
35
+
"workflowDefaultInputs": [
36
+
{ "name": "directCommit", "value": true },
37
+
{ "name": "releaseType", "value": "Prerelease" }
38
+
]
39
+
}
40
+
}
41
+
]
42
+
}
43
+
```
44
+
45
+
**Important:** When multiple conditional settings blocks match and both define `workflowDefaultInputs`, the arrays are merged following AL-Go's standard behavior for complex setting types (all entries are kept). If the same input name appears in multiple entries, the last matching entry takes precedence.
46
+
47
+
Read more at [workflowDefaultInputs](https://aka.ms/algosettings#workflowDefaultInputs).
48
+
49
+
### Issues
50
+
51
+
- Issue 2039 Error when deploy to environment: NewTemporaryFolder is not recognized
52
+
- Issue 1961 KeyVault access in PR pipeline
53
+
- Discussion 1911 Add support for reportSuppressedDiagnostics
54
+
- Discussion 1968 Parameter for settings passed to CreateDevEnv
55
+
- Issue 1945 Deploy Reference Documentation fails for CI/CD
56
+
- Use Runner_Temp instead of GetTempFolder whenever possible
57
+
- Issue 2016 Running Update AL-Go system files with branches wildcard `*` tries to update _origin_
58
+
- Issue 1960 Deploy Reference Documentation fails
59
+
- Discussion 1952 Set default values on workflow_dispatch input
60
+
61
+
### Deprecations
62
+
63
+
-`unusedALGoSystemFiles` will be removed after October 1st 2026. Please use [`customALGoFiles.filesToExclude`](https://aka.ms/algosettings#customALGoFiles) instead.
64
+
1
65
## v8.0
2
66
3
67
### Mechanism to overwrite complex settings type
@@ -917,7 +981,7 @@ Setting the repo setting "runs-on" to "Ubuntu-latest", followed by running Updat
917
981
### Issues
918
982
919
983
- Issue #143 Commit Message for **Increment Version Number** workflow
920
-
- Issue #160 Create local DevEnv aith appDependencyProbingPaths
984
+
- Issue #160 Create local DevEnv with appDependencyProbingPaths
921
985
- Issue #156 Versioningstrategy 2 doesn't use 24h format
0 commit comments