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
# Warn user that 'DeployTo' setting needs to include environment name
367
+
if ($environmentVariableObject.PSObject.Properties.Name-contains"DeployTo") {
368
+
OutputWarning "The environment settings variable contains the property 'DeployTo'. Did you intend to use 'DeployTo$environmentName' instead? The 'DeployTo' property without a specific environment name is not supported."
369
+
}
370
+
# Warn user if 'runs-on', 'shell' or 'ContinuousDeployment' is defined in the environment settings variable, as these are not supported when defined there.
371
+
if ($environmentVariableObject.PSObject.Properties.Name-contains"DeployTo$environmentName") {
if ($environmentVariableObject."DeployTo$environmentName".PSObject.Properties.Name -contains$_) {
374
+
OutputWarning "The property $_ in the DeployTo setting is not supported when defined within a GitHub deployment environment variable. Please define this property elsewhere."
Copy file name to clipboardExpand all lines: RELEASENOTES.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,28 @@
2
2
3
3
AL-Go now offers a dataexplorer dashboard to get started with AL-Go telemetry. Additionally, we've updated the documentation to include a couple of kusto queries if you would rather build your own reports.
4
4
5
+
### Support for AL-Go settings as GitHub environment variable: ALGoEnvSettings
6
+
7
+
AL-Go settings can now be defined in GitHub environment variables. To use this feature, create a new variable under your GitHub environment called `ALGoEnvironmentSettings`. Please note that this variable should not include your environment name.
8
+
9
+
Settings loaded this way, will only be available during the Deploy step of the CI/CD or Publish to Environment actions, but not the Build step, making it most suitable for the [DeployTo setting](https://aka.ms/algosettings#deployto). Settings defined in this variable will take priority over any setting defined in AL-Go repo, org or settings files.
10
+
11
+
The contents of the variable should be a JSON block, similar to any other settings file or variable. When defining the `DeployTo\<EnvName>` setting in this variable, it should still include the environment name. Eg:
12
+
13
+
```
14
+
{
15
+
DeployToProduction {
16
+
"Branches": [
17
+
"*"
18
+
],
19
+
"includeTestAppsInSandboxEnvironment": false,
20
+
"excludeAppIds": [ 1234 ]
21
+
}
22
+
}
23
+
```
24
+
25
+
Please note, that due to certain security limitations, the properties `runs-on`, `shell` and `ContinousDeployment` of the `DeployTo` setting will <ins>**NOT**</ins> be respected if defined in a GitHub environment variable. To use these properties, please keep them defined elsewhere, such as your AL-Go settings file or Org/Repo settings variables.
26
+
5
27
### Issues
6
28
7
29
- Issue 1770 Wrong type of _projects_ setting in settings schema
0 commit comments