Skip to content

Commit b70f580

Browse files
craigshoemakercraigshoemaker
committed
replace indicator
1 parent a810a76 commit b70f580

File tree

2 files changed

+70
-70
lines changed

2 files changed

+70
-70
lines changed

‎articles/container-apps/manage-secrets.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -276,9 +276,9 @@ In this example, the application connection string is declared as `queue-connect
276276
"environment_id": {
277277
"type": "String"
278278
},
279-
"key_vault_secret_uri": { 👈🏼👈🏼
280-
"type": "String" 👈🏼👈🏼
281-
} 👈🏼👈🏼
279+
"key_vault_secret_uri": { ⬅️
280+
"type": "String" ⬅️
281+
} ⬅️
282282
},
283283
"variables": {},
284284
"resources": [
@@ -292,12 +292,12 @@ In this example, the application connection string is declared as `queue-connect
292292
"managedEnvironmentId": "[parameters('environment_id')]",
293293
"configuration": {
294294
"activeRevisionsMode": "single",
295-
"secrets": [ 👈🏼👈🏼
296-
{ 👈🏼👈🏼
297-
"name": "queue-connection-string", 👈🏼👈🏼
298-
"keyVaultUrl": "[parameters('key_vault_secret_uri')", 👈🏼👈🏼
299-
"identity": "system" 👈🏼👈🏼
300-
}] 👈🏼👈🏼
295+
"secrets": [ ⬅️
296+
{ ⬅️
297+
"name": "queue-connection-string", ⬅️
298+
"keyVaultUrl": "[parameters('key_vault_secret_uri')", ⬅️
299+
"identity": "system" ⬅️
300+
}] ⬅️
301301
},
302302
"template": {
303303
"containers": [
@@ -310,8 +310,8 @@ In this example, the application connection string is declared as `queue-connect
310310
"value": "myqueue"
311311
},
312312
{
313-
"name": "ConnectionString", 👈🏼👈🏼
314-
"secretRef": "queue-connection-string" 👈🏼👈🏼
313+
"name": "ConnectionString", ⬅️
314+
"secretRef": "queue-connection-string" ⬅️
315315
}
316316
]
317317
}
@@ -327,8 +327,8 @@ In this example, the application connection string is declared as `queue-connect
327327
"queueLength": 100,
328328
"auth": [
329329
{
330-
"secretRef": "queue-connection-string", 👈🏼👈🏼
331-
"triggerParameter": "connection" 👈🏼👈🏼
330+
"secretRef": "queue-connection-string", ⬅️
331+
"triggerParameter": "connection" ⬅️
332332
}
333333
]
334334
}

‎articles/container-apps/scale-app.md

Lines changed: 57 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -382,7 +382,7 @@ First, you define the type and metadata of the scale rule.
382382

383383
```yaml
384384
triggers:
385-
- type: azure-servicebus 👈🏼👈🏼
385+
- type: azure-servicebus ⬅️
386386
metadata:
387387
queueName: my-queue
388388
namespace: service-bus-namespace
@@ -397,7 +397,7 @@ First, you define the type and metadata of the scale rule.
397397
{
398398
name: 'azure-servicebus-queue-rule'
399399
custom: {
400-
type: 'azure-servicebus' 👈🏼👈🏼
400+
type: 'azure-servicebus' ⬅️
401401
metadata: {
402402
queueName: 'my-queue'
403403
namespace: 'service-bus-namespace'
@@ -415,9 +415,9 @@ First, you define the type and metadata of the scale rule.
415415
triggers:
416416
- type: azure-servicebus
417417
metadata:
418-
queueName: my-queue 👈🏼👈🏼
419-
namespace: service-bus-namespace 👈🏼👈🏼
420-
messageCount: "5" 👈🏼👈🏼
418+
queueName: my-queue ⬅️
419+
namespace: service-bus-namespace ⬅️
420+
messageCount: "5" ⬅️
421421
```
422422

423423
1. In the Bicep template, add all metadata values to the `custom.metadata` section of the scale rule.
@@ -430,9 +430,9 @@ rules: [
430430
custom: {
431431
type: 'azure-servicebus'
432432
metadata: {
433-
queueName: 'my-queue' 👈🏼👈🏼
434-
namespace: 'service-bus-namespace' 👈🏼👈🏼
435-
messageCount: '5' 👈🏼👈🏼
433+
queueName: 'my-queue' ⬅️
434+
namespace: 'service-bus-namespace' ⬅️
435+
messageCount: '5' ⬅️
436436
}
437437
}
438438
}
@@ -462,17 +462,17 @@ KEDA scalers can use secrets in a [TriggerAuthentication](https://keda.sh/docs/l
462462
namespace: my-project
463463
type: Opaque
464464
data:
465-
connection-string-secret: <SERVICE_BUS_CONNECTION_STRING> 👈🏼👈🏼
465+
connection-string-secret: <SERVICE_BUS_CONNECTION_STRING> ⬅️
466466
---
467467
apiVersion: keda.sh/v1alpha1
468468
kind: TriggerAuthentication
469469
metadata:
470470
name: azure-servicebus-auth
471471
spec:
472472
secretTargetRef:
473-
- parameter: connection 👈🏼👈🏼
474-
name: my-secrets 👈🏼👈🏼
475-
key: connection-string-secret 👈🏼👈🏼
473+
- parameter: connection ⬅️
474+
name: my-secrets ⬅️
475+
key: connection-string-secret ⬅️
476476
---
477477
apiVersion: keda.sh/v1alpha1
478478
kind: ScaledObject
@@ -510,10 +510,10 @@ KEDA scalers can use secrets in a [TriggerAuthentication](https://keda.sh/docs/l
510510
configuration: {
511511
...
512512
secrets: [
513-
{ 👈🏼👈🏼
514-
name: 'connection-string-secret' 👈🏼👈🏼
515-
value: '<SERVICE_BUS_CONNECTION_STRING>' 👈🏼👈🏼
516-
} 👈🏼👈🏼
513+
{ ⬅️
514+
name: 'connection-string-secret' ⬅️
515+
value: '<SERVICE_BUS_CONNECTION_STRING>' ⬅️
516+
} ⬅️
517517
]
518518
}
519519
template: {
@@ -637,7 +637,7 @@ First, you define the type and metadata of the scale rule.
637637

638638
```yml
639639
triggers:
640-
- type: azure-servicebus 👈🏼👈🏼
640+
- type: azure-servicebus ⬅️
641641
metadata:
642642
queueName: my-queue
643643
namespace: service-bus-namespace
@@ -652,7 +652,7 @@ First, you define the type and metadata of the scale rule.
652652
{
653653
"name": "azure-servicebus-queue-rule",
654654
"custom": {
655-
"type": "azure-servicebus", 👈🏼👈🏼
655+
"type": "azure-servicebus", ⬅️
656656
"metadata": {
657657
"queueName": "my-queue",
658658
"namespace": "service-bus-namespace",
@@ -670,9 +670,9 @@ First, you define the type and metadata of the scale rule.
670670
triggers:
671671
- type: azure-servicebus
672672
metadata:
673-
queueName: my-queue 👈🏼👈🏼
674-
namespace: service-bus-namespace 👈🏼👈🏼
675-
messageCount: "5" 👈🏼👈🏼
673+
queueName: my-queue ⬅️
674+
namespace: service-bus-namespace ⬅️
675+
messageCount: "5" ⬅️
676676
```
677677

678678
1. In the ARM template, add all metadata values to the `custom.metadata` section of the scale rule.
@@ -685,9 +685,9 @@ First, you define the type and metadata of the scale rule.
685685
"custom": {
686686
"type": "azure-servicebus",
687687
"metadata": {
688-
"queueName": "my-queue", 👈🏼👈🏼
689-
"namespace": "service-bus-namespace", 👈🏼👈🏼
690-
"messageCount": "5" 👈🏼👈🏼
688+
"queueName": "my-queue", ⬅️
689+
"namespace": "service-bus-namespace", ⬅️
690+
"messageCount": "5" ⬅️
691691
}
692692
}
693693
}
@@ -717,17 +717,17 @@ KEDA scalers can use secrets in a [TriggerAuthentication](https://keda.sh/docs/l
717717
namespace: my-project
718718
type: Opaque
719719
data:
720-
connection-string-secret: <SERVICE_BUS_CONNECTION_STRING> 👈🏼👈🏼
720+
connection-string-secret: <SERVICE_BUS_CONNECTION_STRING> ⬅️
721721
---
722722
apiVersion: keda.sh/v1alpha1
723723
kind: TriggerAuthentication
724724
metadata:
725725
name: azure-servicebus-auth
726726
spec:
727727
secretTargetRef:
728-
- parameter: connection 👈🏼👈🏼
729-
name: my-secrets 👈🏼👈🏼
730-
key: connection-string-secret 👈🏼👈🏼
728+
- parameter: connection ⬅️
729+
name: my-secrets ⬅️
730+
key: connection-string-secret ⬅️
731731
---
732732
apiVersion: keda.sh/v1alpha1
733733
kind: ScaledObject
@@ -767,10 +767,10 @@ KEDA scalers can use secrets in a [TriggerAuthentication](https://keda.sh/docs/l
767767
"configuration": {
768768
...
769769
"secrets": [
770-
{ 👈🏼👈🏼
771-
"name": "connection-string-secret", 👈🏼👈🏼
772-
"value": "<SERVICE_BUS_CONNECTION_STRING>" 👈🏼👈🏼
773-
} 👈🏼👈🏼
770+
{ ⬅️
771+
"name": "connection-string-secret", ⬅️
772+
"value": "<SERVICE_BUS_CONNECTION_STRING>" ⬅️
773+
} ⬅️
774774
]
775775
},
776776
"template": {
@@ -789,10 +789,10 @@ KEDA scalers can use secrets in a [TriggerAuthentication](https://keda.sh/docs/l
789789
"messageCount": "5"
790790
},
791791
"auth": [
792-
{ 👈🏼👈🏼
793-
"secretRef": "connection-string-secret", 👈🏼👈🏼
794-
"triggerParameter": "connection" 👈🏼👈🏼
795-
} 👈🏼👈🏼
792+
{ ⬅️
793+
"secretRef": "connection-string-secret", ⬅️
794+
"triggerParameter": "connection" ⬅️
795+
} ⬅️
796796
]
797797
}
798798
}
@@ -845,7 +845,7 @@ To learn more about using managed identity with scale rules, see [Managed identi
845845

846846
```yml
847847
triggers:
848-
- type: azure-servicebus 👈🏼👈🏼
848+
- type: azure-servicebus ⬅️
849849
metadata:
850850
queueName: my-queue
851851
namespace: service-bus-namespace
@@ -864,7 +864,7 @@ To learn more about using managed identity with scale rules, see [Managed identi
864864
--max-replicas 5 \
865865
--secrets "connection-string-secret=<SERVICE_BUS_CONNECTION_STRING>" \
866866
--scale-rule-name azure-servicebus-queue-rule \
867-
--scale-rule-type azure-servicebus \ 👈🏼👈🏼
867+
--scale-rule-type azure-servicebus \ ⬅️
868868
--scale-rule-metadata "queueName=my-queue" \
869869
"namespace=service-bus-namespace" \
870870
"messageCount=5" \
@@ -877,9 +877,9 @@ To learn more about using managed identity with scale rules, see [Managed identi
877877
triggers:
878878
- type: azure-servicebus
879879
metadata:
880-
queueName: my-queue 👈🏼👈🏼
881-
namespace: service-bus-namespace 👈🏼👈🏼
882-
messageCount: "5" 👈🏼👈🏼
880+
queueName: my-queue ⬅️
881+
namespace: service-bus-namespace ⬅️
882+
messageCount: "5" ⬅️
883883
```
884884

885885
1. In the CLI command, set the `--scale-rule-metadata` parameter to the metadata values.
@@ -897,9 +897,9 @@ To learn more about using managed identity with scale rules, see [Managed identi
897897
--secrets "connection-string-secret=<SERVICE_BUS_CONNECTION_STRING>" \
898898
--scale-rule-name azure-servicebus-queue-rule \
899899
--scale-rule-type azure-servicebus \
900-
--scale-rule-metadata "queueName=my-queue" \ 👈🏼👈🏼
901-
"namespace=service-bus-namespace" \ 👈🏼👈🏼
902-
"messageCount=5" \ 👈🏼👈🏼
900+
--scale-rule-metadata "queueName=my-queue" \ ⬅️
901+
"namespace=service-bus-namespace" \ ⬅️
902+
"messageCount=5" \ ⬅️
903903
--scale-rule-auth "connection=connection-string-secret"
904904
```
905905

@@ -923,17 +923,17 @@ A KEDA scaler supports secrets in a [TriggerAuthentication](https://keda.sh/docs
923923
namespace: my-project
924924
type: Opaque
925925
data:
926-
connection-string-secret: <SERVICE_BUS_CONNECTION_STRING> 👈🏼👈🏼
926+
connection-string-secret: <SERVICE_BUS_CONNECTION_STRING> ⬅️
927927
---
928928
apiVersion: keda.sh/v1alpha1
929929
kind: TriggerAuthentication
930930
metadata:
931931
name: azure-servicebus-auth
932932
spec:
933933
secretTargetRef:
934-
- parameter: connection 👈🏼👈🏼
935-
name: my-secrets 👈🏼👈🏼
936-
key: connection-string-secret 👈🏼👈🏼
934+
- parameter: connection ⬅️
935+
name: my-secrets ⬅️
936+
key: connection-string-secret ⬅️
937937
---
938938
apiVersion: keda.sh/v1alpha1
939939
kind: ScaledObject
@@ -969,13 +969,13 @@ A KEDA scaler supports secrets in a [TriggerAuthentication](https://keda.sh/docs
969969
--image <CONTAINER_IMAGE_LOCATION>
970970
--min-replicas 0 \
971971
--max-replicas 5 \
972-
--secrets "connection-string-secret=<SERVICE_BUS_CONNECTION_STRING>" \ 👈🏼👈🏼
972+
--secrets "connection-string-secret=<SERVICE_BUS_CONNECTION_STRING>" \ ⬅️
973973
--scale-rule-name azure-servicebus-queue-rule \
974974
--scale-rule-type azure-servicebus \
975975
--scale-rule-metadata "queueName=my-queue" \
976976
"namespace=service-bus-namespace" \
977977
"messageCount=5" \
978-
--scale-rule-auth "connection=connection-string-secret" 👈🏼👈🏼
978+
--scale-rule-auth "connection=connection-string-secret" ⬅️
979979
```
980980

981981
#### Using managed identity
@@ -1022,7 +1022,7 @@ az containerapp create \
10221022

10231023
```yml
10241024
triggers:
1025-
- type: azure-servicebus 👈🏼👈🏼
1025+
- type: azure-servicebus ⬅️
10261026
metadata:
10271027
queueName: my-queue
10281028
namespace: service-bus-namespace
@@ -1037,9 +1037,9 @@ az containerapp create \
10371037
triggers:
10381038
- type: azure-servicebus
10391039
metadata:
1040-
queueName: my-queue 👈🏼👈🏼
1041-
namespace: service-bus-namespace 👈🏼👈🏼
1042-
messageCount: "5" 👈🏼👈🏼
1040+
queueName: my-queue ⬅️
1041+
namespace: service-bus-namespace ⬅️
1042+
messageCount: "5" ⬅️
10431043
```
10441044

10451045
1. In the portal, find the *Metadata* section and select **Add**. Enter the name and value for each item in the KEDA `ScaledObject` specification metadata section.
@@ -1070,9 +1070,9 @@ Container Apps scale rules support secrets-based authentication. Scale rules for
10701070
name: azure-servicebus-auth
10711071
spec:
10721072
secretTargetRef:
1073-
- parameter: connection 👈🏼👈🏼
1074-
name: my-secrets 👈🏼👈🏼
1075-
key: connection-string-secret 👈🏼👈🏼
1073+
- parameter: connection ⬅️
1074+
name: my-secrets ⬅️
1075+
key: connection-string-secret ⬅️
10761076
---
10771077
apiVersion: keda.sh/v1alpha1
10781078
kind: ScaledObject

0 commit comments

Comments
 (0)