Skip to content

Commit d59cfa9

Browse files
author
Tom Barnes
committed
Custom overrides doc update.
1 parent d328bf1 commit d59cfa9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

site/config-overrides.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -285,7 +285,7 @@ The following `jdbc-testDS.xml` override template demonstrates setting the URL,
285285
* Configure the name of the configuration map in the domain CR `configOverrides` field.
286286
* Configure the names of each secret in domain CR.
287287
* If the secret contains the WebLogic admin `username` and `password` keys, set the domain CR `webLogicCredentialsSecret` field.
288-
* For all other secrets, add them to domain CR `configOverrideSecrets` field.
288+
* For all other secrets, add them to domain CR `configOverrideSecrets` field. Note: this must be in an array format even if you only add one secret (see the sample domain resource yaml below).
289289
* Any override changes require stopping all WebLogic pods, applying your domain resource (if it changed), and restarting the WebLogic pods before they can take effect.
290290
* Custom override changes on an existing running domain, such as updating an override configuration map, a secret, or a domain resource, will not take effect until all running WebLogic Server pods in your domain are shutdown (so no servers are left running), and the domain is subsequently restarted with your new domain resource (if it changed), or with you existing domain resource (if you haven't changed it).
291291
* To stop all running WebLogic Server pods in your domain, apply a changed resource, and then start/restart the domain:

0 commit comments

Comments
 (0)