Skip to content

Commit 1874f68

Browse files
committedJul 22, 2024·
Merge branch 'docs-4.2.1' into 'main'
Docs 4.2.1 See merge request weblogic-cloud/weblogic-deploy-tooling!1725
2 parents f5b823c + 040011b commit 1874f68

File tree

4 files changed

+109
-47
lines changed

4 files changed

+109
-47
lines changed
 

‎documentation/4.0/content/developer/ReleaseProcess.md

+10-6
Original file line numberDiff line numberDiff line change
@@ -46,21 +46,25 @@ The best practice is to write the release notes that will be published to GitHub
4646
- `WDT_SCM_REPO_URL` - set to the browsable URL to the project (e.g., `https://github.com/oracle/weblogic-deploy-tooling`)
4747
- `WDT_SCM_REPO_CONN` - set to the clonable URL for the project (e.g., `git@github.com:oracle/weblogic-deploy-tooling.git`)
4848

49-
2. In the `weblogic-deploy-tooling` project directory, run the `mvn -B release:prepare release:perform` command.
49+
2. When releasing as part of the Oracle infrastructure, you *must* make sure to wait until all Jenkins build activity
50+
associated with the `main` branch is complete prior to starting the release process.
51+
52+
3. In the `weblogic-deploy-tooling` project directory, run the `mvn -B release:prepare release:perform` command.
5053

5154
- If the next development version is changing the major or minor version, override the default `developmentVersion`
5255
property on the command line. For example,
5356
`mvn -B -DdevelopmentVersion=3.2.0-SNAPSHOT release:prepare release:perform`.
5457
- If your SSH private key has a passphrase, watch the build closely because it will prompt for your passphrase multiple times.
5558
Failure to enter it in a timely manner may result in a failure.
5659

57-
3. If the build fails, run the `mvn -B release:rollback` command to undo it and start over from Step 2., after correcting the issue.
58-
4. After the software has been released, move on to the GitHub Release Process.
60+
4. If the build fails, run the `mvn -B release:rollback` command to undo it and start over from Step 2., after correcting the issue.
61+
5. After the software has been released, move on to the GitHub Release Process.
5962

6063
### GitHub release process
6164
Note that this process relies on the WDT installers being in your local Maven repository. As such, it is critical for
6265
the same user to run these steps on the same machine as the steps from the previous section!
6366

64-
1. Save the release notes in the file `<wdt-project-directory>/target/ReleaseNotes.md`.
65-
2. Run the command `mvn -f github-release.xml -DreleaseVersion=<release version number> verify` to create the draft GitHub Release.
66-
3. Log into [GitHub](https://github.com/oracle/weblogic-deploy-tooling), go to the Releases page, review/edit the draft release, and then publish the release.
67+
1. Prior to starting the GitHub release, you *must* wait until all Jenkins activity triggered by the release is complete.
68+
2. Save the release notes in the file `<wdt-project-directory>/target/ReleaseNotes.md`.
69+
3. Run the command `mvn -f github-release.xml -DreleaseVersion=<release version number> verify` to create the draft GitHub Release.
70+
4. Log into [GitHub](https://github.com/oracle/weblogic-deploy-tooling), go to the Releases page, review/edit the draft release, and then publish the release.

‎documentation/4.0/content/release-notes/_index.md

+23-40
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
+++
22
title = "Release Notes"
33
date = 2024-01-09T18:27:38-05:00
4-
weight = 70
4+
weight = 69
55
pre = "<b> </b>"
66
+++
77

88

9-
### Changes in Release 4.2.0
9+
### Changes in Release 4.2.1
1010
- [Major New Features](#major-new-features)
1111
- [Other Changes](#other-changes)
1212
- [Bugs Fixes](#bug-fixes)
@@ -17,46 +17,29 @@ pre = "<b> </b>"
1717
None
1818

1919
#### Other Changes
20-
- #1682 - Added support for discovering built-in security provider data in online mode. This includes
21-
DefaultAuthenticator users and groups, XACMLAuthorizer policies, XACMLRoleMapper roles, and DefaultCredentialMapper
22-
user/password credential mappings. As with other discovery features, default values are filtered out and will not
23-
appear in the model. By default, discovering users and credential mappings require the use of WDT encryption so that
24-
no clear text passwords are stored in the model or variable files.
25-
- #1682 - Normalized XACMLRoleMapper role handling by removing the previous discovery of XACMLRoleMapper roles (that was
26-
not working with newer versions of WebLogic anyway) and removing version limitations during provisioning.
27-
- #1682 - Deprecated the `-use_encryption` command-line argument and replaced it with `-passphrase_prompt` to make the
28-
purpose of the argument clearer.
29-
- #1682 - Relaxed the JDK 8 requirement to use WDT encryption. Later versions of JDK 7 have the necessary algorithm
30-
support so now WDT determines at startup whether the underlying JDK supports WDT encryption or not.
31-
- #1682 - Used the values of the `-admin_user` and provided password to populate the `domainInfo:/AdminUserName` and
32-
`domainInfo:/AdminPassword` fields when discovering security provider data.
33-
- #1688 - Enhanced variable tokenization support to include passwords in discovered security provider data.
34-
- #1689 - Added the ability to discover the OPSS wallet when running in online mode.
35-
- #1693 - Changed the `wko`, `wko-dii` (deprecated), and `wko-pv` target values to refer to the latest versions instead
36-
of WebLogic Kubernetes Operator 3 versions. Added `wko3`, `wko3-dii`, and `wko3-pv` to accommodate users that still
37-
require the ability to use these older versions.
38-
- #1697 - Added support for the Prepare Model Tool to preserve any one-way hashed passwords in the model.
39-
- #1700 - Added support for storing XACML policy and role definitions that could not be converted to their original
40-
policy and role expressions as XACML files in the archive file.
20+
- #1717, #1728 - Extended the API integration between WebLogic Kubernetes Toolkit UI and WDT to pass back the encrypted
21+
passwords when running the Prepare Model Tool from the WebLogic Kubernetes Toolkit UI.
22+
- #1722 - Added logic to detect a situation where the user specified in `domainInfo:/AdminUserName` is also listed in
23+
the `topology:/Security/User` list of users and update the `topology:/Security/User` user's `Password` field to be
24+
the same as that specified in `domainInfo:/AdminPassword`.
25+
- #1723 - Added support for the WebLogic Server 12.2.1.4 and 14.1.1 July 2024 PSUs.
4126

4227
#### Bug Fixes
43-
- #1687 - Fixed a problem with the Discover Domain Tool not properly handling Data Source user names with spaces with
44-
older versions of WebLogic Server.
45-
- #1690 - Fixed a problem with determining the default security realm name that caused it to always be `myrealm`.
46-
- #1692 - Fixed a misleading error message when the model points to an application outside of the archive file that
47-
does not exist.
48-
- #1695 - Fixed an issue where the WebLogic Kubernetes Operator `domain.yaml` was including a placeholder for the
49-
`domainHome` attribute in all cases so that the WebLogic Image Tool could populate it when creating the image.
50-
This was occurring even in use cases where the WebLogic Image Tool did not have this information. WDT no longer does
51-
this and will only include the `domainHome` in the case where the user has specified it on the command line,
52-
or in the `kubernetes` section of the model.
53-
- #1698 - Fixed issues with the new messages related to the security provider data discovery features.
54-
- #1701 - Moved the TestSummaryHandler logging class out of the installer since it is only meant for supporting unit tests.
55-
- #1702 - Fixed a bug in deployment plan discovery for exploded applications.
56-
- #1703 - Fixed a bug in discovery of `domainBin` scripts.
57-
- #1705 - Added missing validation for the `WLSUserPasswordCredentialMappings` section.
58-
- #1706 - Fixed a validation bug that was causing lax validation to fail when archive entries were missing.
59-
- #1707 - Fixed a bug in the handling of the `ActiveContextHandlerEntry` attribute of an `Auditor` security provider.
28+
- #1713 - Added logic at startup to detect when WDT logging is not properly configured.
29+
- #1715 - Fixed a bug where the `domainInfo:/OPSSWalletPassphrase` field was not properly handled when using the
30+
Prepare Model Tool or when using the Discover Domain Tool with the `-target` argument.
31+
- #1716 - Fixed the Discover Domain Tool documentation to add missing command-line arguments.
32+
- #1718 - Fixed an issue with the `NativeVersionEnabled` attribute of `NMProperties` not working correctly when running
33+
the Update Domain Tool.
34+
- #1720 - Fixed an issue with RCU pre-check error handling that was causing an unhandled Jython error.
35+
- #1721 - Fixed a bug in the SSH directory listing command for a remote Unix machine.
36+
- #1724 - Fixed an off-by-one error when using the Archive Helper Tool's `remove custom` command with a name that starts
37+
with `wlsdeploy/custom/` or `config/wlsdeploy/custom/` that was causing the specified location to not be removed.
38+
- #1727, #1729 - Fixed an issue with Create Domain Tool's RCU pre-check functionality that was causing a Jython
39+
AttributeException for `set` when the STB DataSource was defined in the `resources:/JDBCSystemResource` section of the
40+
model and specifying one or more JDBC driver properties.
41+
- #1730 - Fixed an issue where an application or library deployment plan was not being collected when the `SourcePath`
42+
contained an excluded location like `@@ORACLE_HOME@@`.
6043

6144
#### Known Issues
6245
- SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
+++
2+
title = "Release 4.2.0"
3+
date = 2024-01-09T18:27:38-05:00
4+
weight = 70
5+
pre = "<b> </b>"
6+
+++
7+
8+
9+
### Changes in Release 4.2.0
10+
- [Major New Features](#major-new-features)
11+
- [Other Changes](#other-changes)
12+
- [Bugs Fixes](#bug-fixes)
13+
- [Known Issues](#known-issues)
14+
15+
16+
#### Major New Features
17+
None
18+
19+
#### Other Changes
20+
- #1682 - Added support for discovering built-in security provider data in online mode. This includes
21+
DefaultAuthenticator users and groups, XACMLAuthorizer policies, XACMLRoleMapper roles, and DefaultCredentialMapper
22+
user/password credential mappings. As with other discovery features, default values are filtered out and will not
23+
appear in the model. By default, discovering users and credential mappings require the use of WDT encryption so that
24+
no clear text passwords are stored in the model or variable files.
25+
- #1682 - Normalized XACMLRoleMapper role handling by removing the previous discovery of XACMLRoleMapper roles (that was
26+
not working with newer versions of WebLogic anyway) and removing version limitations during provisioning.
27+
- #1682 - Deprecated the `-use_encryption` command-line argument and replaced it with `-passphrase_prompt` to make the
28+
purpose of the argument clearer.
29+
- #1682 - Relaxed the JDK 8 requirement to use WDT encryption. Later versions of JDK 7 have the necessary algorithm
30+
support so now WDT determines at startup whether the underlying JDK supports WDT encryption or not.
31+
- #1682 - Used the values of the `-admin_user` and provided password to populate the `domainInfo:/AdminUserName` and
32+
`domainInfo:/AdminPassword` fields when discovering security provider data.
33+
- #1688 - Enhanced variable tokenization support to include passwords in discovered security provider data.
34+
- #1689 - Added the ability to discover the OPSS wallet when running in online mode.
35+
- #1693 - Changed the `wko`, `wko-dii` (deprecated), and `wko-pv` target values to refer to the latest versions instead
36+
of WebLogic Kubernetes Operator 3 versions. Added `wko3`, `wko3-dii`, and `wko3-pv` to accommodate users that still
37+
require the ability to use these older versions.
38+
- #1697 - Added support for the Prepare Model Tool to preserve any one-way hashed passwords in the model.
39+
- #1700 - Added support for storing XACML policy and role definitions that could not be converted to their original
40+
policy and role expressions as XACML files in the archive file.
41+
42+
#### Bug Fixes
43+
- #1687 - Fixed a problem with the Discover Domain Tool not properly handling Data Source user names with spaces with
44+
older versions of WebLogic Server.
45+
- #1690 - Fixed a problem with determining the default security realm name that caused it to always be `myrealm`.
46+
- #1692 - Fixed a misleading error message when the model points to an application outside of the archive file that
47+
does not exist.
48+
- #1695 - Fixed an issue where the WebLogic Kubernetes Operator `domain.yaml` was including a placeholder for the
49+
`domainHome` attribute in all cases so that the WebLogic Image Tool could populate it when creating the image.
50+
This was occurring even in use cases where the WebLogic Image Tool did not have this information. WDT no longer does
51+
this and will only include the `domainHome` in the case where the user has specified it on the command line,
52+
or in the `kubernetes` section of the model.
53+
- #1698 - Fixed issues with the new messages related to the security provider data discovery features.
54+
- #1701 - Moved the TestSummaryHandler logging class out of the installer since it is only meant for supporting unit tests.
55+
- #1702 - Fixed a bug in deployment plan discovery for exploded applications.
56+
- #1703 - Fixed a bug in discovery of `domainBin` scripts.
57+
- #1705 - Added missing validation for the `WLSUserPasswordCredentialMappings` section.
58+
- #1706 - Fixed a validation bug that was causing lax validation to fail when archive entries were missing.
59+
- #1707 - Fixed a bug in the handling of the `ActiveContextHandlerEntry` attribute of an `Auditor` security provider.
60+
61+
#### Known Issues
62+
- SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
63+
the 12.2.1.4.0 GA release fails with the following error, as mentioned at https://github.com/hierynomus/sshj/issues/895.
64+
Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.
65+
66+
```shell
67+
SEVERE Messages:
68+
1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC
69+
```
70+
71+
- SSH support for the Update Domain Tool and Deploy Apps Tool does not work when using an archive file and the remote
72+
WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
73+
issue with the SSHJ library WDT is using. See https://github.com/hierynomus/sshj/issues/929 for more information.
74+
75+
See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

‎pom.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@
4545
<slf4j.version>2.0.13</slf4j.version>
4646
<jzlib.version>1.1.3</jzlib.version>
4747
<asn.one.version>0.6.0</asn.one.version>
48-
<jline.version>3.26.2</jline.version>
48+
<jline.version>3.26.3</jline.version>
4949
<jansi.version>2.4.1</jansi.version>
5050
<junit.version>5.10.3</junit.version>
5151
<wdt.scm.repo.url>${env.WDT_SCM_REPO_URL}</wdt.scm.repo.url>

0 commit comments

Comments
 (0)
Please sign in to comment.