Merge remote-tracking branch 'upstream/next' into update-main-1

src/data/nav.yaml

@@ -95,25 +95,28 @@
             - title: Installing an Ecosystem using Helm
               path: /docs/ecosystem/ecosystem-installing-k8s
             - title: Configuring authentication
-              path: /docs/ecosystem/ecosystem-authentication              
-            - title: Test streams
-              path: /docs/writing-own-tests/test-streams
-            - title: Managing integrated test runs
-              path: /docs/ecosystem/ecosystem-manage-cps
+              path: /docs/ecosystem/ecosystem-authentication
             - title: Configuring an Ecosystem using resource files
               path: /docs/ecosystem/cps-yaml  
+            - title: Updating credentials in an Ecosystem
+              path: /docs/ecosystem/ecosystem-update-creds 
+            - title: Managing configuration properties
+              path: /docs/ecosystem/ecosystem-manage-cps              
+        - title: Managing tests in a Galasa Ecosystem
+          path: /docs/manage-ecosystem
+          items: 
+            - title: Test streams
+              path: /docs/manage-ecosystem/test-streams
             - title: Selecting tests to run in an Ecosystem
-              path: /docs/cli-command-reference/ecosystem-cli-runs-prepare
+              path: /docs/manage-ecosystem/ecosystem-cli-runs-prepare
             - title: Running tests in an Ecosystem
-              path: /docs/cli-command-reference/ecosystem-cli-runs-submit
+              path: /docs/manage-ecosystem/ecosystem-cli-runs-submit
             - title: Retrying and cancelling tests
-              path: /docs/cli-command-reference/runs-reset-cancel
+              path: /docs/manage-ecosystem/runs-reset-cancel
             - title: Viewing test run results 
-              path: /docs/cli-command-reference/cli-runs-get
+              path: /docs/manage-ecosystem/cli-runs-get
             - title: Downloading test artifacts 
-              path: /docs/cli-command-reference/ecosystem-cli-runs-download
-            - title: Updating credentials in an Ecosystem
-              path: /docs/ecosystem/ecosystem-update-creds  
+              path: /docs/manage-ecosystem/ecosystem-cli-runs-download
         - title: Upgrading
           path: /docs/upgrading  
         - title: Managers

src/markdown-pages/docs/ecosystem/ecosystem-manage-cps.md

@@ -1,6 +1,6 @@
 ---
 path: "/docs/ecosystem/ecosystem-manage-cps"
-title: "Managing integrated test runs"
+title: "Managing configuration properties"
 ---
 
 [Retrieving namespaces](#retrievingnamespaces)<br>

src/markdown-pages/docs/manage-ecosystem/manage-ecosystem.md

@@ -0,0 +1,10 @@
+---
+path: "/docs/manage-ecosystem"
+title: "Managing tests in a Galasa Ecosystem"
+---
+
+Read the topics contained in this section to understand how to simply and effectively manage the scheduling and running of large numbers of Galasa tests in automation in a Galasa Ecosystem. You can group your tests using the test stream function, select groups of tests to run, retry and cancel failed tests, view results in a number of formats, and download test artifacts quickly and easily by using the Galasa CLI. 
+
+
+
+

src/markdown-pages/docs/cli-command-reference/runs-download.md → src/markdown-pages/docs/manage-ecosystem/runs-download.md

@@ -1,5 +1,5 @@
 ---
-path: "/docs/cli-command-reference/ecosystem-cli-runs-download"
+path: "/docs/manage-ecosystem/ecosystem-cli-runs-download"
 title: "Downloading test artifacts"
 ---
 

src/markdown-pages/docs/cli-command-reference/runs-get.md → src/markdown-pages/docs/manage-ecosystem/runs-get.md

@@ -1,5 +1,5 @@
 ---
-path: "/docs/cli-command-reference/cli-runs-get"
+path: "/docs/manage-ecosystem/cli-runs-get"
 title: "Viewing test run results"
 ---
 

src/markdown-pages/docs/cli-command-reference/runs-prepare.md → src/markdown-pages/docs/manage-ecosystem/runs-prepare.md

@@ -1,11 +1,11 @@
 ---
-path: "/docs/cli-command-reference/ecosystem-cli-runs-prepare"
+path: "/docs/manage-ecosystem/ecosystem-cli-runs-prepare"
 title: "Selecting tests to run in an Ecosystem"
 ---
 
 If you have a group of tests that you want to run in batch, the simplest way to do this is by defining these tests inside a portfolio. You can create a portfolio of tests by using the `runs prepare` command. You can build the portfolio from single or multiple [test streams](https://galasa.dev/docs/writing-own-tests/test-streams).
 
-This portfolio of tests can then be run by using the [runs submit command](/docs/cli-command-reference/ecosystem-cli-runs-submit). When you submit the tests to run, you need specify only the portfolio name on the command, rather than listing all of the classes.
+This portfolio of tests can then be run by using the [runs submit command](/docs/manage-ecosystem/ecosystem-cli-runs-submit). When you submit the tests to run, you need specify only the portfolio name on the command, rather than listing all of the classes.
 
 ## Working with the `runs prepare` command
 

src/markdown-pages/docs/cli-command-reference/runs-reset-cancel.md → src/markdown-pages/docs/manage-ecosystem/runs-reset-cancel.md

@@ -1,5 +1,5 @@
 ---
-path: "/docs/cli-command-reference/runs-reset-cancel"
+path: "/docs/manage-ecosystem/runs-reset-cancel"
 title: "Retrying and cancelling tests"
 ---
 

src/markdown-pages/docs/cli-command-reference/runs-submit.md → src/markdown-pages/docs/manage-ecosystem/runs-submit.md

@@ -1,19 +1,19 @@
 ---
-path: "/docs/cli-command-reference/ecosystem-cli-runs-submit"
+path: "/docs/manage-ecosystem/ecosystem-cli-runs-submit"
 title: "Running tests in an Ecosystem"
 ---
 
 The `runs submit` command submits and monitors tests in the Galasa Ecosystem. Tests can be input either from a portfolio or directly from a test package.
 
-For information about creating a portfolio by using the Galasa CLI, see the documentation for the [runs prepare](/docs/cli-command-reference/ecosystem-cli-runs-prepare) command.
+For information about creating a portfolio by using the Galasa CLI, see the documentation for the [runs prepare](/docs/manage-ecosystem/ecosystem-cli-runs-prepare) command.
 
 ## Working with the `runs submit` command
 
 The following section provides a subset of examples of how you can use the `runs submit` command to complete various tasks, for example, getting help, submitting tests, and setting overrides. The examples build on the Galasa SimBank tests, which you can run non-locally if you have an ecosystem that is running SimPlatform.
 
 ### Submitting tests to an ecosystem from a portfolio
 
-The following example assumes that you have created a `my_portfolio.yaml` portfolio by using the [runs prepare](/docs/cli-command-reference/ecosystem-cli-runs-prepare) command. The command submits tests from the `my_portfolio.yaml` portfolio, and specifies the following settings.
+The following example assumes that you have created a `my_portfolio.yaml` portfolio by using the [runs prepare](/docs/manage-ecosystem/ecosystem-cli-runs-prepare) command. The command submits tests from the `my_portfolio.yaml` portfolio, and specifies the following settings.
 
 On Mac or Unix: