Target environment doc changes #1070
Conversation
|
|
||
| #### The WebLogic Kubernetes Operator target | ||
|
|
||
| This target environment can be applied by providing the command-line argument `-target wko`. It will provide this additional processing: |
There was a problem hiding this comment.
This target environment can be applied by providing -> (to change this from passive to active voice) -> You can apply this target environment by providing (if you agree, then please make this change globally)
| ```yaml | ||
| PasswordEncrypted: '@@SECRET:@@ENV:DOMAIN_UID@@-jdbc-generic1:password@@' | ||
| ``` | ||
| When a domain is created or updated using a model with these tokens, the environment variable `DOMAIN_UID` should be set to the domain's UID, and secrets with corresponding names should have been created. See [Model Tokens]({{< relref "/concepts/model#model-tokens" >}}) for more details about using secret tokens. |
There was a problem hiding this comment.
See [Model Tokens]({{< relref "/concepts/model#model-tokens" >}}) for more details about using secret tokens. -> For more details about using secret tokens, see [Model Tokens]({{< relref "/concepts/model#model-tokens" >}}). (this is the standard Oracle style for providing this type of cross-reference; please make this change globally)
| ``` | ||
| The script should be updated with correct `<user>` and `<password>` values as required. It may be necessary to change the `NAMESPACE` and `DOMAIN_UID` variables at the top of the script if they are different in the target environment. | ||
|
|
||
| The script performs a check to determine if any generated secret names are more than 63 characters in length, since that will prevent them from being mounted correctly in the Kubernetes environment. If any secret names exceed this limit, they will need to be shortened in this script, in the model files, and in the domain resource file. Each shortened name should be distinct from other secret names. |
There was a problem hiding this comment.
since -> because (since – don't use to mean for the reason of; use because. Use since only for matters of time, for example, since the last time the program was run.)
Re-organize and add secret credentials information.
Internal Jira WDT-507