Merge branch 'main' into sdvTemp

src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli.md

@@ -50,7 +50,7 @@ In order to run the Galasa SimBanks tests you need to add some configuration inf
 
 The SimBank tests are held in the <a href="https://github.com/galasa-dev/simplatform" target="_blank"> Galasa simplatform repository</a> in GitHub. To start running the tests you need to clone the repository, if you have not already done so. To find out how to clone the cli repository, follow the instruction in the `Launching SimBank` section in the [Exploring Galasa SimBank online](simbank-cli) documentation.
 
-After cloning the repository, complete the following steps to run the SimBankIVT test that is provided with Galasa. The following example uses SimBank OBR version `0.25.0` and Galasa uber OBR version `0.32.0`.
+After cloning the repository, complete the following steps to run the SimBankIVT test that is provided with Galasa. The following example uses SimBank OBR version `0.25.0` and Galasa uber OBR version `0.33.0`.
 
 You can find the version of the `dev.galasa.simbank.obr` that you are using by looking in the `pom.xml` file in the `dev.galasa.simbank.obr` folder. The `dev.galasa.uber.obr` is the OBR that contains all the bundles that are needed for Galasa to work including Managers, any required dependencies, the framework, etc. The version of the `dev.galasa.uber.obr` depends on which version of Galasa you have installed.
 

src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md

@@ -259,21 +259,21 @@ You can then deploy your Galasa tests to a Maven repository and set up a test st
 
 ## Upgrading the Galasa Ecosystem
 
-To upgrade the Galasa Ecosystem to use a newer version of Galasa, for example version 0.32.0, run the following command:
+To upgrade the Galasa Ecosystem to use a newer version of Galasa, for example version 0.33.0, run the following command:
 
 
 On Mac or Unix:
 
 ```console
 helm upgrade <release-name> galasa/ecosystem --reuse-values \
---set galasaVersion=0.32.0 --wait
+--set galasaVersion=0.33.0 --wait
 ```
 
 On Windows (Powershell):
 
 ```console
 helm upgrade <release-name> galasa/ecosystem --reuse-values `
---set galasaVersion=0.32.0 --wait
+--set galasaVersion=0.33.0 --wait
 ```
 
 where:<br>

src/markdown-pages/faqs-galasa.md

@@ -13,6 +13,7 @@ Use the following sections to scan for questions and problems that have been rai
 [What is the purpose of `imageTag`?](#k)<br><br>
 [What is the connection between z/OS terminal and application?](#l)<br><br>
 [Why is my test, which is running on a local LPAR, failing at the Provision Generate phase with the error "Caused by: dev.galasa.zos.ZosManagerException: Insufficent capacity for images in cluster..."?](#m)<br><br>
+[I have a testcase that needs to connect to an external resource with SSL. Is there a preferred way to do this with Galasa if I do not have access to the default truststore?](#n)<br><br>
 
 
 ### <a name="a"></a>How can I generate screenshot output when running my tests locally?
@@ -152,3 +153,7 @@ Normal operation of an Ecosystem includes a resource monitor which looks for thi
 
 Clearing out the `dss.properties` file resets the counters down to zero again. It is safe to do this providing that no tests are running. In principle, if you run multiple tests in parallel, you can see some of this limiting safety feature start failing tests even if you did not clean out the DSS. It is worth noting that if you always clear out the `dss.properties` file, the run name of tests always start from the same number, as the latest test number allocated counter is also kept there.
 
+### <a name="n"></a> I have a testcase that needs to connect to an external resource with SSL. Is there a preferred way to do this with Galasa if I do not have access to the default truststore? 
+
+For local tests, in the `bootstrap.properties` file, you can use `galasactl.jvm.local.launch.options=-Xmx80m -Xms20m`.
+When the galasactl program launches the JVM it will add those options to the command-line.

src/markdown-pages/highlights.md

@@ -17,8 +17,21 @@ We have the following available Slack channels:
 
 Access the Galasa source code in [GitHub](https://github.com/galasa-dev) and open issues in the [project management repository](https://github.com/galasa-dev/projectmanagement).
 
+## 0.33.0 - Release Highlights
 
-## 0.32.0 - Release Highlights
+- Authentication when interacting with an Ecosystem is now mandatory. You need to authenticate with an Ecosystem in order to use its API server or to use any galasactl commands that interact with an Ecosystem. 
+
+- CouchDB is upgraded to version 3.3.3. If you upgrade your Ecosystem to Galasa version 0.33.0, CouchDB will be upgraded. Though we don't anticipate any problems with the Helm chart upgrading CouchDB in-situ, we recommend that you follow the usual safety practices of backing up your data prior to any upgrade. You can then apply the backup to the new CouchDB pod after it is created. CouchDB cannot be downgraded after upgrading.
+
+- Maven and Gradle plugins now accept a personal access token when publishing a test catalog to the Ecosystem.
+
+- Various bug fixes
+
+- Various documentation enhancements, including property updates for the CICS TS and z/OS Managers, and information on updating credentials in an Ecosystem.
+
+
+<details>
+<summary><b>0.32.0 - Release Highlights</b></summary>
 
 - CLI updates: 
 
@@ -33,6 +46,7 @@ Access the Galasa source code in [GitHub](https://github.com/galasa-dev) and ope
 - The Eclipse plug-in for Galasa is no longer supported. You can work with Galasa version 0.32.0 and later by using the Galasa command line interface (CLI).
 
 - Various documentation enhancements.
+</details> 
 
 
 

src/pages/index.js

@@ -126,7 +126,7 @@ const IndexPage = () => (
             Learn more
           </Button>
           <Button target={"/releases"} flash={true} isPrimary={true}>
-            0.32.0 highlights
+            0.33.0 highlights
           </Button>
         </div>
       </div>