Merge pull request #6828 from OpenLiberty/staging

Staging to vNext, 23.0.0.8 issues

.github/ISSUE_TEMPLATE/release-issue-template.md

@@ -15,13 +15,13 @@ assignees: ''
 - **Estimnated GA Date:** 
 - 
 ### Notes
-**List any special concerns for this release that are not already tracked in anothere issue, such as release dependencies, Javadoc updates, support level changes, planned docs refresh, etc.**
+**List any special concerns for this release that are not already tracked in another issue, such as release dependencies, Javadoc updates, support level changes, planned docs refresh, etc.**
 
 ### Release checklist
 - [ ] If any Jakarta or MicroProfile API docs are updated with this release, work with development to get the updates merged to the `docs-javadoc` repo (1-2 weeks before GA)
 - [ ] All issues with a label for this release and any other issues included in the release milestone are completed and closed, with content merged to vNext. (~3 working days before GA)
 - [ ] All autogenerated documentation is refreshed on draft (~3 working days before GA)
-- [ ] Confirm with team that docs are frozen and no more updates will be sent to vNext (3 working days before GA).
-- [ ] Verify main feature epic statuses to ensure that all targeteted features will be included in the release (before closing doc feature issues and again 1-2 working days before GA).
+- [ ] Confirm with the team that docs are frozen and no more updates will be sent to vNext (3 working days before GA).
+- [ ] Verify main feature epic statuses to ensure that all targeted features will be included in the release (before closing doc feature issues and again 1-2 working days before GA).
 - [ ] [Publish docs to production on GA](https://github.com/OpenLiberty/docs-playbook#publishing-a-new-release-of-open-liberty-docs)
 - [ ] Determine if a docs refresh will be needed before the next upcoming release. If so, make a note of the date and leave this issue open until complete. If not, close this issue. 

modules/ROOT/pages/security-vulnerabilities.adoc

@@ -28,6 +28,13 @@ The `CWWKF0012I` message uses the word "installed", but it lists features that a
 |===
 |CVE |CVSS score by X-Force® |Vulnerability assessment |Versions affected |Version fixed |Notes
 
+|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38737[CVE-2023-38737]
+|5.9
+|Denial of service
+|22.0.0.13 - 23.0.0.7
+|23.0.0.8
+|Affects the feature:restfulWS-3.0[] and feature:restfulWS-3.1[] features
+
 |http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28867[CVE-2023-28867]
 |7.5
 |Denial of service

modules/reference/nav.adoc

@@ -77,4 +77,8 @@ include::reference:partial$feature-nav.adoc[]
   ** xref:diff/mp-41-50-diff.adoc[Differences between MicroProfile 5.0 and 4.1]
   ** xref:diff/mp-33-40-diff.adoc[Differences between MicroProfile 4.0 and 3.3]
   ** xref:diff/mp-22-30-diff.adoc[Differences between MicroProfile 3.0 and 2.2]
-  ** xref:diff/mp-21-22-diff.adoc[Differences between MicroProfile 2.2 and 2.1]
+  ** xref:diff/mp-21-22-diff.adoc[Differences between MicroProfile 2.2 and 2.1]
+
+include::reference:partial$feature-nav-api-openliberty.adoc[]
+
+include::reference:partial$feature-nav-spi-openliberty.adoc[]

modules/reference/pages/command/server-create.adoc

@@ -18,7 +18,7 @@ The `server create` command creates an Open Liberty server.
 Create a server called `myserver`:
 
 ----
-server create myserver
+server create myserver 
 ----
 
 == Syntax
@@ -27,29 +27,49 @@ Run the command from the `_path_to_liberty_/wlp/bin` directory.
 
 [subs=+quotes]
 ----
-server create _serverName_
+server create _serverName_ [_options_]
 ----
 
 serverName::
 A name for the server. If no server is specified, a server called `defaultServer` is automatically created.
 
-Naming constraints:
+This command is subject to the following naming constraints:
 
 * Use only Unicode alphanumeric (e.g. 0-9, a-z, A-Z), underscore (_), dash (-), plus (+), and period (.) characters.
 * Do not begin the name with a dash (-) or a period (.).
 * Be aware that your file system, operating system, or compressed file directory might impose more restrictions.
 
-When the server is created successfully, you receive the message: `Server _serverName_ created`.
+When the server is created successfully, you receive the following message: `Server _serverName_ created`.
 
 A directory with the name of the new server is created under the `${wlp.user.dir}/servers` directory, which contains the configuration of the new server. The HTTP port numbers for the new server are assigned to default values and are shown in the generated `server.xml` file to make it easy to edit them.
 
-If the specified server exists, then no server is created and you receive an exception message:
+If the specified server already exists, then no server is created and you receive an exception message.
 
+////
 ----
 CWWKE0005E: The runtime environment could not be launched.
 CWWKE0045E: It was not possible to create the server called server_name because
 the server directory C:\wlp\usr\servers\server_name already exists.
 ----
+////
+
+== Options
+
+.Options for the server create command
+[%header,cols=2*]
+|===
+|Option
+|Description
+
+|--no-password
+|When this option is specified, no default keystore password is generated when the server is created.
+
+|--template=_templateName_
+|This option specifies the name of a template to use when a new server is created. The template is a customized `server.xml` or `client.xml` file with pre-configured features and settings for a particular programming model. 
+For example, `server create myServer --template=jakartaee10`.
+
+By default, the available templates are in the `wlp/templates/servers` and `wlp/templates/clients` directories.
+|===
 
 == Exit codes
 

modules/reference/pages/config/server-configuration-overview.adoc

@@ -266,7 +266,7 @@ server run myserver -- --variableName=variableValue
 ----
 
 Environment variables can be accessed as variables.
-As of version 19.0.0.3, you can reference the environment variable name directly.
+You can reference the environment variable name directly.
 If the variable cannot be resolved as specified, the `server.xml` file looks for the following variations on the environment variable name:
 
 * Replace all non-alphanumeric characters with the underscore character (`_`)
@@ -278,16 +278,7 @@ For example, if you enter `${my.env.var}` in the `server.xml` file, it looks for
 . my_env_var
 . MY_ENV_VAR
 
-For versions 19.0.0.3 and earlier, you can access environment variables by adding `env.` to the start of the environment variable name, as shown in the following example:
-
-[source,xml]
-----
-<httpEndpoint id="defaultHttpEndpoint"
-              host="${env.HOST}"
-              httpPort="9080" />
-----
-
-Variables can be loaded from files located in directories that are specified by the `VARIABLE_SOURCE_DIRS` environment variable.
+The `VARIABLE_SOURCE_DIRS` environment variable specifies directories from which variables can be loaded.
 If this environment variable is not specified, the default location for the variable directory is `${server.config.dir}/variables`.
 To define a list of directories as the value for this variable, separate each directory with the path separator for your operating system. For Windows, the path separator is a semicolon (`;`). For Unix-based systems, the path separator is a colon (`:`).