Skip to content

Commit b220ca6

Browse files
committed
Clarify explanation of authentication with secret.
1 parent b92d114 commit b220ca6

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

articles/container-apps/scale-app.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -329,17 +329,19 @@ KEDA scalers can use secrets in a [TriggerAuthentication](https://keda.sh/docs/l
329329

330330
1. Find the `TriggerAuthentication` object referenced by the KEDA `ScaledObject` specification.
331331

332-
1. From the KEDA specification, find each `secretTargetRef` of the `TriggerAuthentication` object and its associated secret.
332+
1. In the `TriggerAuthentication` object, find each `secretTargetRef` and its associated secret.
333333

334334
:::code language="yml" source="~/azure-docs-snippets-pr/container-apps/keda-azure-service-bus-auth.yml" highlight="8,16,17,18":::
335335

336-
1. In the ARM template, add all entries to the `auth` array of the scale rule.
336+
1. In the ARM template, for each secret:
337337

338-
1. Add a [secret](./manage-secrets.md) to the container app's `secrets` array containing the secret value.
338+
1. Add a [secret](./manage-secrets.md) to the container app's `secrets` array containing the secret name and value.
339339

340-
1. Set the value of the `triggerParameter` property to the value of the `TriggerAuthentication`'s `key` property.
340+
1. Add an entry to the `auth` array of the scale rule.
341341

342-
1. Set the value of the `secretRef` property to the name of the Container Apps secret.
342+
1. Set the value of the `triggerParameter` property to the value of the `secretTargetRef`'s `parameter` property.
343+
344+
1. Set the value of the `secretRef` property to the name of the `secretTargetRef`'s `key` property.
343345

344346
:::code language="json" source="~/azure-docs-snippets-pr/container-apps/container-apps-azure-service-bus-rule-1.json" highlight="10,11,12,13,32,33,34,35":::
345347

0 commit comments

Comments
 (0)