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
Modify Samples to Call Function App and Web App Samples via Default Hostname (#76)
* Added azlocal start-interception to all README files
* Fix Web App + SQL Sample
* Change secret name to be compliant with validate.sh
* updated runner
* skip if already exists
* remove the pre-existing microsoft-prod.list
* upgraded azurerm provider
* Modify Samples to Call Function App and Web App Samples via Default Hostname
* Fixed resource group name
---------
Co-authored-by: Dris.S <53239451+DrisDary@users.noreply.github.com>
Copy file name to clipboardExpand all lines: samples/function-app-managed-identity/python/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ All deployment methods have been fully tested with both user-assigned and system
86
86
87
87
## Test
88
88
89
-
Once the resources and serverless application have been deployed, you can use the `test.sh` script below to copy a sample file to the `input` container and monitor whether the Azure Functions App processes the input blob file and generates a result file in the `output` container.
89
+
Once the resources and serverless application have been deployed, you can use the [test.sh](./scripts/test.sh) script below to copy a sample file to the `input` container and monitor whether the Azure Functions App processes the input blob file and generates a result file in the `output` container.
Copy file name to clipboardExpand all lines: samples/function-app-storage-http/dotnet/README.md
+1-185Lines changed: 1 addition & 185 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,194 +163,10 @@ All deployment methods have been fully tested against Azure and the LocalStack f
163
163
164
164
Use the [call-http-triggers.sh](./scripts/call-http-triggers.sh) script to quickly test the sample's HTTP-triggered Azure Functions and verify player status or game session details. The script below demonstrates three methods for calling HTTP-triggered functions:
165
165
166
-
1.**Through the LocalStack for Azure emulator**: Call the function app via the emulator using its default host name. The emulator acts as a proxy to the functionapp.
166
+
1.**Via the default hostname**: Call the function app via the default hostname `<function-app-name>.azurewebsites.azure.localhost.localstack.cloud:4566`.
167
167
2.**Via localhost and host port mapped to the container's port**: Use `127.0.0.1` with the host port mapped to the container's port `80`.
168
168
3.**Via container IP address**: Use the app container's IP address on port `80`. This technique is only available when accessing the function app from the Docker host machine.
169
169
170
-
```bash
171
-
#!/bin/bash
172
-
173
-
get_docker_container_name_by_prefix() {
174
-
local app_prefix="$1"
175
-
local container_name
176
-
177
-
# Check if Docker is running
178
-
if! docker info >/dev/null 2>&1;then
179
-
echo"Error: Docker is not running">&2
180
-
return 1
181
-
fi
182
-
183
-
echo"Looking for containers with names starting with [$app_prefix]...">&2
184
-
185
-
# Find the container using grep
186
-
container_name=$(docker ps --format "{{.Names}}"| grep "^${app_prefix}"| head -1)
187
-
188
-
if [ -z"$container_name" ];then
189
-
echo"Error: No running container found with name starting with [$app_prefix]">&2
# Call the GET HTTP trigger function that returns a player status in a specified game session via the container IP address
328
-
echo"Calling HTTP trigger function to retrieve player [$player_name] status in game session [$game_session] via container IP address [$container_ip]..."
You can use [Azure Storage Explorer](https://learn.microsoft.com/en-us/azure/storage/storage-explorer/vs-azure-tools-storage-manage-with-storage-explorer) to confirm that your Azure Function app creates the expected storage entities in the emulated storage account. To do this:
# Call the GET HTTP trigger function that returns a player status in a specified game session via the function hostname
143
+
echo"Calling HTTP trigger function to retrieve player [$player_name] status in game session [$game_session] via function hostname [$function_host_name]..."
0 commit comments