Skip to content

Commit e2eeac4

Browse files
committed
Adding secret example configuration 5
1 parent ba431ee commit e2eeac4

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/learn/getting-started-secret-management.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -242,22 +242,22 @@ $ git push origin my-branch
242242

243243
. Verify the Secret in the Cluster
244244

245-
.. Once ArgoCD has applied the changes, verify that the `mysecret-secret` has been created in the `config-demo` namespace:
245+
.. Once ArgoCD has applied the changes, verify that the `config-demo-mysecret` has been created in the `config-demo` namespace:
246246
+
247247
[source,terminal]
248248
----
249-
$ oc get secret mysecret-secret -n config-demo
249+
$ oc get secret config-demo-mysecret -n config-demo
250250
----
251251

252252
.. Check the contents of the secret if necessary:
253253
+
254254
[source,terminal]
255255
----
256-
$ oc describe secret mysecret-secret -n config-demo
256+
$ oc describe secret config-demo-mysecret -n config-demo
257257
----
258258

259259
== Outcome
260-
After completing these steps, the new `mysecret-secret` should be created and visible in the `config-demo` namespace, populated with the relevant data extracted from the Vault.
260+
After completing these steps, the new `config-demo-mysecret` should be created and visible in the `config-demo` namespace, populated with the relevant data extracted from the Vault.
261261

262262

263263
== Next Steps

0 commit comments

Comments
 (0)