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
Support versioning when installing site extensions in AzureAppServiceManageV0 task (#21060)
* Support versioning when installing site extensions in AzureAppServiceManageV0 task
* Fix the failing build and align test stub/spy method with other tasks
* Update versions
* Update readme removing statement about env variable for FF as untrue
* Don't force installation when version is "latest" and site extension already installed with latest version
* Do not install site extension if specified version is already installed
Copy file name to clipboardExpand all lines: Tasks/AzureAppServiceManageV0/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,8 @@ The task is used to manage an existing Azure App Service. The mandatory fields a
53
53
54
54
***Install Extensions:** The task can also be used to [install site extensions](https://www.siteextensions.net/packages) on the App Service. Site Extensions run on Microsoft Azure App Service. You can install set of tools as site extension such as [PHP Composer](https://www.siteextensions.net/packages/ComposerExtension/) or the right version of [Python](https://www.siteextensions.net/packages?q=Python). The App Service will be restarted to make sure latest changes take effect. Please note that extensions are only supported only for Web App on Windows.
55
55
56
+
-**Versioned Extension Support (Preview):** You can now specify extensions as `name@version` (e.g., `[email protected]`). If a version is specified, that exact version will be installed. If you specify `latest` as the version, the latest available version will be installed (in case it already has the latest version, installation will be skipped). If no version is specified, the extension will only be installed if it is not already present. Example: `[email protected], OtherExtension@latest, LegacyExtension`.
57
+
56
58
## Output variable
57
59
When provided a variable name, the variable will be populated with the the local installation path of the selected extension. In case of multiple extensions selected for installation, provide comma separated list of variables that saves the local path for each of the selected extension in the order it appears in the Install Extension field. Example: outputVariable1, outputVariable2
0 commit comments