Skip to content

Commit d8a5a50

Browse files
mpershinampershina
authored
Merge pull request #146 from migtools/7.3.0_Release-notes
Release notes for 7.3.0
2 parents ad1a305 + 483d125 commit d8a5a50

File tree

4 files changed

+94
-5
lines changed

4 files changed

+94
-5
lines changed

‎docs/release-notes/master.adoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,13 @@ include::topics/making-open-source-more-inclusive.adoc[]
2121
[id="mta-7-3-0"]
2222
== {ProductShortName} 7.3.0
2323

24+
include::topics/ref_new-features-7-3-0.adoc[leveloffset=+2]
25+
26+
include::topics/ref_fixed-issues-7-3-0.adoc[leveloffset=+2]
27+
2428
include::topics/ref_known-issues-7-3-0.adoc[leveloffset=+2]
2529

30+
2631
[id="mta-7-2-2"]
2732
== {ProductShortName} 7.2.2
2833

‎docs/topics/ref_fixed-issues-7-3-0.adoc

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
:_newdoc-version: 2.18.3
2+
:_template-generated: 2025-05-12
3+
4+
:_mod-docs-content-type: REFERENCE
5+
6+
[id="fixed-issues-7-3-0_{context}"]
7+
= Fixed issues
8+
9+
This section provides the following bug fixes and resolves issues and other problems that have a significant impact on the {ProductFullName} 7.3.0.
10+
11+
.MTA CLI now excludes the `target` folder when analyzing compiled Java Maven projects
12+
Previously, for compiled Java Maven projects, the {ProductShortName} CLI included incidents by analyzing the `target` folder. This generated different reports for Java Maven projects before and after running the `mvn-clean-package` command. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5078[(MTA-5078)]
13+
14+
.Application credential update now triggers a new discovery task
15+
Previously, when you update the source or Maven credential for an application, a new discovery task was not triggered in the {ProductShortName} {WebName}. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5121[(MTA-5121)]

‎docs/topics/ref_known-issues-7-3-0.adoc

Lines changed: 26 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
:_template-generated: 2024-12-04
1+
:_newdoc-version: 2.18.3
2+
:_template-generated: 2025-04-29
3+
24
:_mod-docs-content-type: REFERENCE
35

46
[id="known-issues-7-3-0_{context}"]
57
= Known issues
68

79
This section provides highlighted known issues in {ProductFullName} version 7.3.0.
810

9-
.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
10-
When you analyze non-Java applications, {ProductShortName} initiates the analysis in containerless mode. Workaround: set the `--run-local=false` flag to analyze non-Java applications. link:https://issues.redhat.com/browse/MTA-5068[MTA-5068]
11-
=======
11+
1212
.`.NET` Framework application analysis fails in the {ProductShortName} {CLIName}
1313
When you analyze `.NET` Framework applications in Windows containers using the {ProductShortName} {CLIName}, the analysis fails for the following environment variables:
1414

@@ -18,4 +18,25 @@ When you analyze `.NET` Framework applications in Windows containers using the {
1818

1919
Workaround: Use the following version of the Dotnet provider image:
2020
`set DOTNET_PROVIDER_IMG=quay.io/konveyor/dotnet-external-provider:v0.5.0`
21-
link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
21+
22+
link:https://issues.redhat.com/browse/MTA-5203[(MTA-5203)]
23+
24+
.Non-Java applications are analyzed in containerless mode in the {ProductShortName} CLI
25+
When you analyze non-Java applications, {ProductShortName} initiates the analysis in containerless mode.
26+
27+
Workaround: set the `--run-local=false` flag to analyze non-Java applications. link:https://issues.redhat.com/browse/MTA-5068[(MTA-5068)]
28+
29+
30+
.Application analysis fails to get a list of dependencies for Node.js in the {ProductShortName} UI
31+
32+
When you run an application analysis for the Node.js language provider by using the {ProductShortName} user-interface (UI), the analysis completes with the following error is displayed in the analysis log:
33+
34+
----
35+
level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'
36+
----
37+
38+
Workaround: Set the `Analysis Mode` setting to `source-only`.
39+
40+
NOTE: The Node.js provider does not have a dependency capability. Therefore, a dependency list cannot be generated. The same applies for the Python provider.
41+
42+
(link:https://issues.redhat.com/browse/MTA-5070[MTA-5070])

‎docs/topics/ref_new-features-7-3-0.adoc

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
:_newdoc-version: 2.18.3
2+
:_template-generated: 2025-04-17
3+
4+
:_mod-docs-content-type: REFERENCE
5+
6+
[id="new-features-7-3-0_{context}"]
7+
= New features
8+
9+
This section provides the new features and improvements of the {ProductFullName} 7.3.0.
10+
11+
12+
.Asset generation is now available in {ProductShortName} CLI
13+
14+
Starting with {ProductShortName} {ProductVersion}, you can run the `discover` and `generate` commands in the {CLIName}:
15+
16+
* The `discover` command generates the discover manifest that preserves the platform and runtime configurations defined in the Cloud Foundry (CF) application manifest.
17+
* The `generate` command uses the discover manifest to generate the deployment manifest in a Kubernetes-native format to prepare it for {ocp-full} deployments. You can also use the command to generate non-Kubernetes manifests such as a Dockerfile.
18+
19+
:FeatureName: Asset generation
20+
include::snippets/developer-preview-admonition.adoc[]
21+
22+
(link:https://issues.redhat.com/browse/MTA-4610[MTA-4610])
23+
24+
.{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
25+
26+
{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`. (link:https://issues.redhat.com/browse/MTA-4540[MTA-4540])
27+
28+
.Listing all languages in an application is now available
29+
30+
In {ProductShortName} {ProductVersion}, you can list all languages in an application by using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the --`override-provider-settings` flag when you analyze the application.
31+
32+
:FeatureName: Listing all languages in an application
33+
include::snippets/developer-preview-admonition.adoc[]
34+
35+
(link:https://issues.redhat.com/browse/MTA-4798[MTA-4798])
36+
37+
38+
.Support for Python and Node.js language providers is now available
39+
40+
In addition to the Java and Go language providers, support for the Python and Node.js language providers is now available for the application analysis in {ProductShortName} 7.3.0. As a result, you can now perform the following actions for these providers in the {ProductShortName} user-interface (UI):
41+
42+
* Add custom migration targets.
43+
* Run custom rules.
44+
45+
:FeatureName: Support for Python and Node.js language providers
46+
include::snippets/technology-preview-admonition.adoc[]
47+
48+
(link:https://issues.redhat.com/browse/MTA-4542[MTA-4542])

0 commit comments

Comments
 (0)