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
{{ message }}
This repository was archived by the owner on Oct 26, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ from the `terraform/` directory you're in after running `terraform apply`.
107
107
108
108
#### The Azure Function
109
109
110
-
In your portal, go to the newly-created Azure Function. Its name will be the `<prefix>` value you put in during the Terraform deployment.
110
+
In your portal, go to the newly-created Azure Function. Its name will be the `<prefix>-serverless-functionapp` value you put in during the Terraform deployment.
111
111
112
112
There are a few things to notice:
113
113
@@ -178,7 +178,7 @@ which ensures that even if somebody were to submit Function code that attempted
178
178
179
179
#### The Logic App
180
180
181
-
In your portal, go to the newly-created Logic App. Its name will be `<prefix>-LA` where `<prefix>` is the value you put in during the Terraform deployment.
181
+
In your portal, go to the newly-created Logic App. Its name will be `<prefix>-serverless-la` where `<prefix>` is the value you put in during the Terraform deployment.
182
182
183
183
##### Execution Logic
184
184
@@ -208,7 +208,7 @@ The important part of the Logic App's configuration is that our Terraform deploy
208
208
209
209
#### Key Vault
210
210
211
-
In your portal, go to the newly-created Key Vault. Its name will be the `<prefix>` value you put in during the Terraform deployment.
211
+
In your portal, go to the newly-created Key Vault. Its name will be the `<prefix>-serverless-kv` value you put in during the Terraform deployment.
212
212
213
213
The important bits of the Key Vault for this sample are the `Events` and `Access Policies` area
214
214
@@ -228,11 +228,11 @@ In order for the Function App to be able to read the values of Key Vault secrets
228
228
229
229
## Bringing it all together
230
230
231
-
If you open the Live Stream for the first Application Insights instance (without the `-2` suffix) you'll see the Function happily logging messages every 5 seconds or so:
231
+
If you open the Live Stream for the first Application Insights instance (with the `-first` suffix) you'll see the Function happily logging messages every 5 seconds or so:
232
232
233
233

234
234
235
-
Moving over to the secondary Application Insights, you'll probably see a screen like this:
235
+
Moving over to the secondary Application Insights (with the `-second` suffix), you'll probably see a screen like this:
0 commit comments