Skip to content

Commit 3a26bcd

Browse files
authored
Update service-fabric-keyvault-references.md
This clarifies that customer must also include the other CSS settings from the original CSS article. They can't just have only the new setting.
1 parent 58f05f6 commit 3a26bcd

File tree

1 file changed

+17
-1
lines changed

1 file changed

+17
-1
lines changed

articles/service-fabric/service-fabric-keyvault-references.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ string secret = Environment.GetEnvironmentVariable("MySecret");
121121

122122
## Use Managed KeyVaultReferences in your application
123123

124-
First, you must enable secret monitoring by upgrading your cluster definition:
124+
First, you must enable secret monitoring by upgrading your cluster definition to add the `EnableSecretMonitoring` setting, in addition to the [other required CSS configurations]((service-fabric-application-secret-store.md)):
125125

126126
```json
127127
"fabricSettings": [
@@ -131,6 +131,22 @@ First, you must enable secret monitoring by upgrading your cluster definition:
131131
{
132132
"name": "EnableSecretMonitoring",
133133
"value": "true"
134+
},
135+
{
136+
"name": "DeployedState",
137+
"value": "enabled"
138+
},
139+
{
140+
"name" : "EncryptionCertificateThumbprint",
141+
"value": "<thumbprint>"
142+
},
143+
{
144+
"name": "MinReplicaSetSize",
145+
"value": "<size>"
146+
},
147+
{
148+
"name": "TargetReplicaSetSize",
149+
"value": "<size>"
134150
}
135151
]
136152
}

0 commit comments

Comments
 (0)