Improve create -o documentation

Author: moreaut

site/creating-domain.md

@@ -139,17 +139,15 @@ Oracle intends to remove these limitations in a future release.
 To execute the script and create a domain, issue the following command:
 
 ```
-# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /scratch/user-projects:
-export OUTPUT_DIR="/path/to/weblogic-operator-output-directory"
-mkdir -p $OUTPUT_DIR
-./create-weblogic-domain.sh –i create-domain-job-inputs.yaml -o $OUTPUT_DIR
+# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
+./create-weblogic-domain.sh –i create-domain-job-inputs.yaml -o /path/to/weblogic-operator-output-directory
 ```
 
 ## What the script does
 
 The script will perform the following steps:
 
-*	Create a directory for the generated Kubernetes YAML files for this domain.  The pathname is $OUTPUT_DIR/weblogic-domains/<domainUID parameter from create-weblogic-domain-inputs.yaml.
+*	Create a directory for the generated Kubernetes YAML files for this domain.  The pathname is /path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID parameter from create-weblogic-domain-inputs.yaml.
 *	Create Kubernetes YAML files based on the provided inputs.
 *	Create a persistent volume for the shared state.
 *	Create a persistent volume claim for that volume.

site/developer.md

@@ -76,16 +76,14 @@ To run the tests, uncomment the following `execution` element in the `pom.xml` f
 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):
 
 ```
-# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /scratch/user-projects:
-export OUTPUT_DIR="/path/to/weblogic-operator-output-directory"
-mkdir -p $OUTPUT_DIR
-./create-weblogic-operator.sh -g -i create-weblogic-operator-inputs.yaml -o $OUTPUT_DIR
+# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
+./create-weblogic-operator.sh -g -i create-weblogic-operator-inputs.yaml -o /path/to/weblogic-operator-output-directory
 ```
 
-This will create a file called `$OUTPUT_DIR/weblogic-operators/weblogic-operator/weblogic-operator-security.yaml`, which you will need to apply to your cluster:
+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:
 
 ```
-kubectl apply -f $OUTPUT_DIR/weblogic-operators/webogic-operator/weblogic-operator-security.yaml
+kubectl apply -f /path/to/weblogic-operator-output-directory/weblogic-operators/webogic-operator/weblogic-operator-security.yaml
 ```
 
 After this is done, and the `execution` is uncommented, the tests will run against your cluster.
@@ -125,10 +123,8 @@ Verify that you have the right image by running `docker images | grep webloogic-
 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:
 
 ```
-# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /scratch/user-projects:
-export OUTPUT_DIR="/path/to/weblogic-operator-output-directory"
-mkdir -p $OUTPUT_DIR
-./create-weblogic-operator.sh -i create-weblogic-operator-inputs.yaml -o $OUTPUT_DIR
+# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
+./create-weblogic-operator.sh -i create-weblogic-operator-inputs.yaml -o /path/to/weblogic-operator-output-directory
 ```
 
 

site/installation.md

@@ -122,17 +122,15 @@ To enable the ELK integration, set the `elkIntegrationEnabled` option to `true`.
 To deploy the operator, run the deployment script and give it the location of your inputs file:
 
 ```
-# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /scratch/user-projects:
-export OUTPUT_DIR="/path/to/weblogic-operator-output-directory"
-mkdir -p $OUTPUT_DIR
-./create-weblogic-operator.sh –i /path/to/create-weblogic-operator-inputs.yaml -o $OUTPUT_DIR
+# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
+./create-weblogic-operator.sh –i /path/to/create-weblogic-operator-inputs.yaml -o /path/to/weblogic-operator-output-directory
 ```
 
 ## What the script does
 
 The script will carry out the following actions:
 
-*	Create a directory for the generated Kubernetes YAML files for this operator.  The pathname is $OUTPUT_DIR/weblogic-operators/<namespace parameter from create-weblogic-operator-inputs.yaml.
+*	Create a directory for the generated Kubernetes YAML files for this operator.  The pathname is /path/to/weblogic-operator-output-directory/weblogic-operators/<namespace parameter from create-weblogic-operator-inputs.yaml.
 *	A set of Kubernetes YAML files will be created from the inputs provided in this directory.
 *	A namespace will be created for the operator.
 *	A service account will be created in that namespace.

site/manually-creating-domain.md

@@ -14,13 +14,11 @@ If creating the domain manually, using a WLST script for example, the domain mus
 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:
 
 ```
-# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /scratch/user-projects:
-export OUTPUT_DIR="/path/to/weblogic-operator-output-directory"
-mkdir -p $OUTPUT_DIR
-./create-weblogic-domain.sh –i create-weblogic-domain-inputs.yaml –g -o $OUTPUT_DIR
+# Choose and create a directory that generated weblogic operator related files will be stored in, e.g. /path/to/weblogic-operator-output-directory
+./create-weblogic-domain.sh –i create-weblogic-domain-inputs.yaml –g -o /path/to/weblogic-operator-output-directory
 ```
 
-The following YAML files will be generated in the $OUTPUT_DIR/weblogic-domains/<domainUID> directory:
+The following YAML files will be generated in the /path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID> directory:
 
 *	`weblogic-domain-persistent-volume.yaml` can be customized and used to create the persistent volume for this domain.
 *	`weblogic-domain-persistent-volume-claim.yaml` can be customized and used to create the persistent volume claim for this domain.