Skip to content

Commit 6e61515

Browse files
committed
Improve create -o documentation
1 parent bf7da3f commit 6e61515

File tree

4 files changed

+30
-10
lines changed

4 files changed

+30
-10
lines changed

site/creating-domain.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -139,8 +139,12 @@ Oracle intends to remove these limitations in a future release.
139139
To execute the script and create a domain, issue the following command:
140140

141141
```
142-
# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
143-
./create-weblogic-domain.sh –i create-domain-job-inputs.yaml -o /path/to/weblogic-operator-output-directory
142+
# Choose and create a directory that generated weblogic operator related files will be stored in,
143+
# e.g. /path/to/weblogic-operator-output-directory
144+
145+
./create-weblogic-domain.sh \
146+
–i create-domain-job-inputs.yaml \
147+
-o /path/to/weblogic-operator-output-directory
144148
```
145149

146150
## What the script does

site/developer.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,12 @@ To run the tests, uncomment the following `execution` element in the `pom.xml` f
7676
These tests assume that the RBAC definitions exist on the Kubernetes cluster. To create them, update the inputs file and run the operator installation script with the "generate only" option as shown below (see the [installation](installation.md) page for details about this script and the inputs):
7777

7878
```
79-
# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
80-
./create-weblogic-operator.sh -g -i create-weblogic-operator-inputs.yaml -o /path/to/weblogic-operator-output-directory
79+
# Choose and create a directory that generated weblogic operator related files will be stored in,
80+
# e.g. /path/to/weblogic-operator-output-directory
81+
82+
./create-weblogic-operator.sh -g \
83+
-i create-weblogic-operator-inputs.yaml \
84+
-o /path/to/weblogic-operator-output-directory
8185
```
8286

8387
This will create a file called `/path/to/weblogic-operator-output-directory/weblogic-operators/weblogic-operator/weblogic-operator-security.yaml`, which you will need to apply to your cluster:
@@ -123,8 +127,12 @@ Verify that you have the right image by running `docker images | grep webloogic-
123127
To create the Kuberentes YAML file to deploy the operator, update the inputs file (`create-weblogic-operator-inputs.yaml`) and make sure the `imagePullPolicy` is set to `Never` and the `image` matches the name you used in your `docker build` command. Then run the operator installation script to deploy the operator:
124128

125129
```
126-
# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
127-
./create-weblogic-operator.sh -i create-weblogic-operator-inputs.yaml -o /path/to/weblogic-operator-output-directory
130+
# Choose and create a directory that generated weblogic operator related files will be stored in,
131+
# e.g. /path/to/weblogic-operator-output-directory
132+
133+
./create-weblogic-operator.sh \
134+
-i create-weblogic-operator-inputs.yaml \
135+
-o /path/to/weblogic-operator-output-directory
128136
```
129137

130138

site/installation.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -122,8 +122,12 @@ To enable the ELK integration, set the `elkIntegrationEnabled` option to `true`.
122122
To deploy the operator, run the deployment script and give it the location of your inputs file:
123123

124124
```
125-
# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
126-
./create-weblogic-operator.sh –i /path/to/create-weblogic-operator-inputs.yaml -o /path/to/weblogic-operator-output-directory
125+
# Choose and create a directory that generated weblogic operator related files will be stored in,
126+
# e.g. /path/to/weblogic-operator-output-directory
127+
128+
./create-weblogic-operator.sh \
129+
–i /path/to/create-weblogic-operator-inputs.yaml \
130+
-o /path/to/weblogic-operator-output-directory
127131
```
128132

129133
## What the script does

site/manually-creating-domain.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,12 @@ If creating the domain manually, using a WLST script for example, the domain mus
1414
The `create-weblogic-domain.sh` script described in the previous section can be executed with the “-g” option, which will cause it to generate the YAML files but take no action at all against the Kubernetes environment. This is a useful way to create the sample YAML files needed to manually create a domain. Execute the script as follows:
1515

1616
```
17-
# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
18-
./create-weblogic-domain.sh –i create-weblogic-domain-inputs.yaml –g -o /path/to/weblogic-operator-output-directory
17+
# Choose and create a directory that generated weblogic operator related files will be stored in,
18+
# e.g. /path/to/weblogic-operator-output-directory
19+
20+
./create-weblogic-domain.sh –g \
21+
–i create-weblogic-domain-inputs.yaml \
22+
-o /path/to/weblogic-operator-output-directory
1923
```
2024

2125
The following YAML files will be generated in the /path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID> directory:

0 commit comments

Comments
 (0)