Move scalingAction.sh

Author: rjeberhard

documentation/site/content/managing-domains/domain-lifecycle/scaling.md

@@ -225,7 +225,7 @@ For more in-depth information on the Kubernetes Horizontal Pod Autoscaler, see [
 The WebLogic Diagnostics Framework (WLDF) is a suite of services and APIs that collect and surface metrics that provide visibility into server and application performance.
 To support automatic scaling of WebLogic clusters in Kubernetes, WLDF provides the Policies and Actions component, which lets you write policy expressions for automatically executing scaling
 operations on a cluster. These policies monitor one or more types of WebLogic Server metrics, such as memory, idle threads, and CPU load.  When the configured threshold
-in a policy is met, the policy is triggered, and the corresponding scaling action is executed.  The WebLogic Kubernetes Operator project provides a shell script, [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/operator/scripts/scaling/scalingAction.sh),
+in a policy is met, the policy is triggered, and the corresponding scaling action is executed.  The WebLogic Kubernetes Operator project provides a shell script, [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/scaling/scalingAction.sh),
 for use as a Script Action, which illustrates how to issue a request to the operator’s REST endpoint.
 
 {{% notice note %}}
@@ -235,14 +235,14 @@ Beginning with operator version 4.0.5, the operator's REST endpoint is disabled
 ##### Configure automatic scaling of WebLogic clusters in Kubernetes with WLDF
 The following steps are provided as a guideline on how to configure a WLDF Policy and Script Action component for issuing scaling requests to the operator's REST endpoint:
 
-1. Copy the [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/operator/scripts/scaling/scalingAction.sh) script to `$DOMAIN_HOME/bin/scripts` so that it's accessible within the Administration Server pod. For more information, see [Configuring Script Actions](https://docs.oracle.com/en/middleware/standalone/weblogic-server/14.1.1.0/wldfc/config_notifications.html#GUID-5CC52534-13CD-40D9-915D-3380C86580F1) in _Configuring and Using the Diagnostics Framework for Oracle WebLogic Server_.
+1. Copy the [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/scaling/scalingAction.sh) script to `$DOMAIN_HOME/bin/scripts` so that it's accessible within the Administration Server pod. For more information, see [Configuring Script Actions](https://docs.oracle.com/en/middleware/standalone/weblogic-server/14.1.1.0/wldfc/config_notifications.html#GUID-5CC52534-13CD-40D9-915D-3380C86580F1) in _Configuring and Using the Diagnostics Framework for Oracle WebLogic Server_.
 
 1. Configure a WLDF policy and action as part of a diagnostic module targeted to the Administration Server. For information about configuring the WLDF Policies and Actions component,
 see [Configuring Policies and Actions](https://docs.oracle.com/en/middleware/standalone/weblogic-server/14.1.1.0/wldfc/config_watch_notif.html#GUID-D3FA8301-AAF2-41CE-A6A5-AB4005849913) in _Configuring and Using the Diagnostics Framework for Oracle WebLogic Server_.
 
      a. Configure a WLDF policy with a rule expression for monitoring WebLogic Server metrics, such as memory, idle threads, and CPU load for example.
 
-     b. Configure a WLDF script action and associate the [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/operator/scripts/scaling/scalingAction.sh) script.
+     b. Configure a WLDF script action and associate the [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/scaling/scalingAction.sh) script.
 
 Important notes about the configuration properties for the Script Action:
 
@@ -369,15 +369,15 @@ details about [Using Prometheus to Automatically Scale WebLogic Clusters on Kube
 
 ### Helpful tips
 #### Debugging scalingAction.sh
-The [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/operator/scripts/scaling/scalingAction.sh) script was designed to be executed within a container of the
+The [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/scaling/scalingAction.sh) script was designed to be executed within a container of the
 Administration Server Pod because the associated diagnostic module is targeted to the Administration Server.
 
 The easiest way to verify and debug the `scalingAction.sh` script is to open a shell on the running Administration Server pod and execute the script on the command line.
 
 The following example illustrates how to open a bash shell on a running Administration Server pod named `domain1-admin-server` and execute the `scriptAction.sh` script.  It assumes that:
 
 * The domain home is in `/u01/oracle/user-projects/domains/domain1` (that is, the domain home is inside an image).
-* The Dockerfile copied [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/operator/scripts/scaling/scalingAction.sh) to `/u01/oracle/user-projects/domains/domain1/bin/scripts/scalingAction.sh`.
+* The Dockerfile copied [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/kubernetes/samples/scripts/scaling/scalingAction.sh) to `/u01/oracle/user-projects/domains/domain1/bin/scripts/scalingAction.sh`.
 
 ```shell
 $ kubectl exec -it domain1-admin-server /bin/bash

integration-tests/src/test/java/oracle/weblogic/kubernetes/actions/impl/Domain.java

@@ -694,7 +694,7 @@ public static boolean scaleClusterWithWLDF(String clusterName,
     logger.info("Copying scalingAction.sh to admin server pod");
     testUntil(
         () -> copyFileToPod(domainNamespace, adminServerPodName, null,
-          Paths.get(PROJECT_ROOT + "/../operator/scripts/scaling/scalingAction.sh"),
+          Paths.get(PROJECT_ROOT + "/../kubernetes/samples/scripts/scaling/scalingAction.sh"),
           Paths.get(domainHomeLocation + "/bin/scripts/scalingAction.sh")),
         logger,
         "Copying scalingAction.sh to admin server pod");
@@ -849,7 +849,7 @@ public static boolean scaleClusterWithScalingActionScript(String clusterName,
     logger.info("Copying scalingAction.sh to admin server pod");
     testUntil(
         () -> copyFileToPod(domainNamespace, adminServerPodName, null,
-          Paths.get(PROJECT_ROOT + "/../operator/scripts/scaling/scalingAction.sh"),
+          Paths.get(PROJECT_ROOT + "/../kubernetes/samples/scripts/scaling/scalingAction.sh"),
           Paths.get("/u01/scalingAction.sh")),
         logger,
         "Copying scalingAction.sh to admin server pod");

operator/scripts/scaling/scalingAction.sh renamed to kubernetes/samples/scripts/scaling/scalingAction.sh

@@ -205,7 +205,7 @@
             </goals>
             <configuration>
               <testSourceDirectory>src/test/sh/scaling</testSourceDirectory>
-              <sourceDirectory>scripts/scaling</sourceDirectory>
+              <sourceDirectory>../kubernetes/samples/scripts/scaling</sourceDirectory>
             </configuration>
           </execution>
         </executions>