From 09cb4bc053b41ec7e19caa54ea2c148e63e213ea Mon Sep 17 00:00:00 2001
From: Mahdi Azarboon <21277296+azarboon@users.noreply.github.com>
Date: Wed, 8 Jan 2025 03:34:34 +0800
Subject: [PATCH] `azurerm_linux_function_app`:  Nuances of Application Code
 Deployment (#28353)

---
 website/docs/r/linux_function_app.html.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/r/linux_function_app.html.markdown b/website/docs/r/linux_function_app.html.markdown
index ff30851c22d2..dd13e8ac0582 100644
--- a/website/docs/r/linux_function_app.html.markdown
+++ b/website/docs/r/linux_function_app.html.markdown
@@ -11,7 +11,7 @@ description: |-
 Manages a Linux Function App.
 
 > [!NOTE]
-> This Terraform resource is limited to creating the Function App resource. To package and deploy your code logic to the Function App, you can use a separate tool, such as [Azure Functions Core Tools](https://learn.microsoft.com/azure/azure-functions/functions-run-local).
+> This Terraform resource is specifically designed to provision the infrastructure for a Function App, which can host one or more individual functions. To package and deploy application code to the Function App, tools like [Azure Functions Core Tools](https://learn.microsoft.com/azure/azure-functions/functions-run-local) or Azure CLI can be utilized. With the current toolset, application code deployment must typically be performed individually for each Function App. It is also important to note that after a Terraform deployment, particularly if the `azurerm_linux_function_app` resource is recreated due to changes in critical properties (such as the OS type, runtime stack, or App Service Plan), previously deployed application code may be removed, necessitating redeployment. This process can, however, be streamlined and automated using custom scripts or CI/CD pipelines.
 
 
 ## Example Usage