Skip to content

Commit 9c2ea67

Browse files
committed
Fix the FTPS publishing stuff
1 parent bdfd844 commit 9c2ea67

File tree

4 files changed

+63
-23
lines changed

4 files changed

+63
-23
lines changed

articles/azure-functions/functions-deployment-technologies.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -36,17 +36,17 @@ Each plan has different behaviors. Not all deployment technologies are available
3636

3737
| Deployment technology | Windows Consumption | Windows Premium | Windows Dedicated | Linux Consumption | Linux Premium | Linux Dedicated |
3838
|-----------------------|:-------------------:|:-------------------------:|:------------------:|:---------------------------:|:-------------:|:---------------:|
39-
| External package URL<sup>1</sup> |||||||
40-
| Zip deploy |||||||
41-
| Docker container | | | | |||
42-
| Web Deploy |||| | | |
43-
| Source control |||| |||
44-
| Local Git<sup>1</sup> |||| |||
45-
| Cloud sync<sup>1</sup> |||| |||
46-
| FTP<sup>1</sup> |||| |||
47-
| In-portal editing<sup>2</sup> |||||✔<sup>3</sup>|✔<sup>3</sup>|
48-
49-
<sup>1</sup> Deployment technology that requires [manual trigger syncing](#trigger-syncing). Deployment Center no longer shows the FTP/FTPS Credentials. If these are still needed then you can download the publishing profile.
39+
| [External package URL](#external-package-url)<sup>1</sup> |||||||
40+
| [Zip deploy](#zip-deploy) |||||||
41+
| [Docker container](#docker-container) | | | | |||
42+
| [Web Deploy](#web-deploy-msdeploy) |||| | | |
43+
| [Source control](#source-control) |||| |||
44+
| [Local Git](#local-git)<sup>1</sup> |||| |||
45+
| [Cloud sync](#cloud-sync)<sup>1</sup> |||| |||
46+
| [FTPS](#ftps)<sup>1</sup> |||| |||
47+
| [In-portal editing](#portal-editing)<sup>2</sup> |||||✔<sup>3</sup>|✔<sup>3</sup>|
48+
49+
<sup>1</sup> Deployment technologies that require you to [manually sync triggers](#trigger-syncing) aren't recommended.
5050
<sup>2</sup> In-portal editing is disabled when code is deployed to your function app from outside the portal. For more information, including language support details for in-portal editing, see [Language support details](supported-languages.md#language-support-details).
5151
<sup>3</sup> In-portal editing is enabled only for HTTP and Timer triggered functions running on Linux in Premium and Dedicated plans.
5252

@@ -186,11 +186,11 @@ Use cloud sync to sync your content from Dropbox and OneDrive to Azure Functions
186186
187187
>__Where app content is stored:__ The app content is in the cloud store, but a local copy is stored on the app file system, which may be backed by Azure Files from the storage account specified when the function app was created.
188188
189-
### FTP
189+
### FTPS
190190

191-
You can use FTP to directly transfer files to Azure Functions.
191+
You can use FTPS to directly transfer files to Azure Functions, athough this deployment method isn't recommended.
192192

193-
>__How to use it:__ Follow the instructions in [Deploy content by using FTP/s](../app-service/deploy-ftp.md&tabs=cli). Note that FTP/S deployment isn't available in the Azure portal, but you can use [Azure CLI](../app-service/deploy-ftp.md&tabs=cli) or [Azure PowerShell](../app-service/deploy-ftp.md&tabs=powershell).
193+
>__How to use it:__ Follow the instructions in [Deploy content by using FTP/s](../app-service/deploy-ftp.md?tabs=cli). Note that FTP/S deployment isn't available in the Azure portal, but you can use [Azure CLI](../app-service/deploy-ftp.md?tabs=cli) or [Azure PowerShell](../app-service/deploy-ftp.md&tabs=powershell).
194194
195195
>__When to use it:__ To reduce the chance of errors, you should avoid using deployment methods that require the additional step of [manually syncing triggers](#trigger-syncing). Use [zip deployment](run-functions-from-deployment-package.md) when possible.
196196

articles/azure-functions/functions-how-to-github-actions.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -48,13 +48,7 @@ Since GitHub Actions uses your publish profile to access your function app durin
4848
4949
### Download your publish profile
5050

51-
To download the publishing profile of your function app:
52-
53-
1. Select the function app's **Overview** page, and then select **Get publish profile**.
54-
55-
:::image type="content" source="media/functions-how-to-github-actions/get-publish-profile.png" alt-text="Download publish profile":::
56-
57-
1. Save and copy the contents of the file.
51+
[!INCLUDE [functions-download-publish-profile](../../includes/functions-download-publish-profile.md)]
5852

5953
### Add the GitHub secret
6054

articles/azure-functions/functions-how-to-use-azure-function-app-settings.md

Lines changed: 33 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,37 @@ Update-AzFunctionAppSetting -Name <FUNCTION_APP_NAME> -ResourceGroupName <RESOUR
8484

8585
When you develop a function app locally, you must maintain local copies of these values in the local.settings.json project file. To learn more, see [Local settings file](functions-develop-local.md#local-settings-file).
8686

87+
## FTPS deployment settings
88+
89+
Azure Functions supports deploying code to your function app by using FTPS. Because this deployment method requires you to [sync triggers](functions-deployment-technologies.md#trigger-syncing), it's not recommended. T securely transfer project files, always use FTPS and not FTP.
90+
91+
You can get the credentials required for FTPS deployment using one of these methods:
92+
93+
### [Portal](#tab/portal)
94+
95+
You can get the FTPS publishing credentials in the Azure portal by downloading the publishing profile for your function app.
96+
97+
> [!IMPORTANT]
98+
> The publishing profile contains important security credentials. You should always secure the downloaded file on your local computer.
99+
100+
[!INCLUDE [functions-download-publish-profile](../../includes/functions-download-publish-profile.md)]
101+
102+
3. In the file, locate the `publishProfile` element with the attribute `publishMethod="FTP"`. In this element, the `publishUrl`, `userName`, and `userPWD` attributes contain the target URL and credentials for FTPS publishing.
103+
104+
### [Azure CLI](#tab/azure-cli)
105+
106+
Run this Azure CLI command that returns the FTPS credentials from the publishing profile.
107+
108+
```azurecli
109+
az functionapp deployment list-publishing-profiles --name <APP_NAME> --resource-group <GROUP_NAME> --query "[?publishMethod=='FTP'].{URL:publishUrl, username:userName, password:userPWD}" -o table
110+
```
111+
112+
In this example, replace `<APP_NAME>` with your function app name and `<GROUP_NAME>` with the resource group. The returned `URL`, `username`, and `password` columns contain the target URL and credentials for FTPS publishing.
113+
114+
### [Azure PowerShell](#tab/azure-powershell)
115+
116+
---
117+
87118
## Hosting plan type
88119

89120
When you create a function app, you also create a hosting plan in which the app runs. A plan can have one or more function apps. The functionality, scaling, and pricing of your functions depend on the type of plan. To learn more, see [Azure Functions hosting options](functions-scale.md).
@@ -98,13 +129,13 @@ The following values indicate the plan type:
98129
| [Premium](functions-premium-plan.md) | **ElasticPremium** | `ElasticPremium` |
99130
| [Dedicated (App Service)](dedicated-plan.md) | Various | Various |
100131

101-
# [Portal](#tab/portal)
132+
### [Portal](#tab/portal)
102133

103134
To determine the type of plan used by your function app, see **App Service plan** in the **Overview** tab for the function app in the [Azure portal](https://portal.azure.com). To see the pricing tier, select the name of the **App Service Plan**, and then select **Properties** from the left pane.
104135

105136
![View scaling plan in the portal](./media/functions-scale/function-app-overview-portal.png)
106137

107-
# [Azure CLI](#tab/azure-cli)
138+
### [Azure CLI](#tab/azure-cli)
108139

109140
Run the following Azure CLI command to get your hosting plan type:
110141

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
author: ggailey777
3+
ms.service: azure-functions
4+
ms.topic: include
5+
ms.date: 09/11/2023
6+
ms.author: glenga
7+
---
8+
9+
To download the publishing profile of your function app:
10+
11+
1. Select the function app's **Overview** page, and then select **Get publish profile**.
12+
13+
:::image type="content" source="media/functions-how-to-github-actions/get-publish-profile.png" alt-text="Download publish profile":::
14+
15+
1. Save and copy the contents of the file.

0 commit comments

Comments
 (0)