-
Notifications
You must be signed in to change notification settings - Fork 8
[WIP] 8.1.0 MTA RNs #299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[WIP] 8.1.0 MTA RNs #299
Changes from 8 commits
0e49ca5
2efa216
34ee9ec
80e29aa
c6f94c2
ba73f7e
da1a5e3
4abd39b
25fdffc
152921d
4a999c2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| :_newdoc-version: 2.18.5 | ||
| :_template-generated: 2026-02-04 | ||
| :_mod-docs-content-type: ASSEMBLY | ||
|
|
||
| ifdef::context[:parent-context-of-mta-8-0: {context}] | ||
|
|
||
| ifndef::context[] | ||
| [id="mta-8-0"] | ||
| endif::[] | ||
| ifdef::context[] | ||
| [id="mta-8-0_{context}"] | ||
| endif::[] | ||
| = {ProductFirstRef} 8.0 | ||
|
|
||
| :context: mta-8-0 | ||
|
|
||
| [role="_abstract"] | ||
| The Release Notes provide high-level coverage of the improvements and additions that have been implemented in {ProductFullName} 8.0. | ||
|
|
||
| include::assembly_mta-8-0-1.adoc[leveloffset=+1] | ||
|
|
||
| include::assembly_mta-8-0-0.adoc[leveloffset=+1] | ||
|
|
||
| ifdef::parent-context-of-mta-8-0[:context: {parent-context-of-mta-8-0}] | ||
| ifndef::parent-context-of-mta-8-0[:!context:] | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| :_newdoc-version: 2.18.5 | ||
| :_template-generated: 2026-02-04 | ||
| :_mod-docs-content-type: ASSEMBLY | ||
|
|
||
| ifdef::context[:parent-context-of-mta-8-1-0: {context}] | ||
|
|
||
| ifndef::context[] | ||
| [id="mta-8-1-0"] | ||
| endif::[] | ||
| ifdef::context[] | ||
| [id="mta-8-1-0_{context}"] | ||
| endif::[] | ||
| = {ProductFirstRef} 8.1 | ||
|
|
||
| :context: mta-8-1-0 | ||
|
|
||
| [role="_abstract"] | ||
| This Release Notes section provides high-level coverage of the improvements and additions that have been implemented in {ProductFullName} 8.1. | ||
|
|
||
| include::topics/release-notes-topics/ref_new-features-and-enhancements-8-1-0.adoc[leveloffset=+1] | ||
|
|
||
| include::topics/release-notes-topics/ref_tech-preview-8-1-0.adoc[leveloffset=+1] | ||
|
|
||
| include::topics/release-notes-topics/ref_known-issues-8-1-0.adoc[leveloffset=+1] | ||
|
|
||
| include::topics/release-notes-topics/ref_fixed-issues-8-1-0.adoc[leveloffset=+1] | ||
|
|
||
|
|
||
| ifdef::parent-context-of-mta-8-1-0[:context: {parent-context-of-mta-8-1-0}] | ||
| ifndef::parent-context-of-mta-8-1-0[:!context:] | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| :_newdoc-version: 2.18.5 | ||
| :_template-generated: 2026-02-13 | ||
| :_mod-docs-content-type: REFERENCE | ||
|
|
||
| [id="fixed-issues-8-1-0_{context}"] | ||
| = Fixed issues | ||
|
|
||
| [role="_abstract"] | ||
| {ProductFirstRef} ({ProductShortName}) version 8.1.0 provides the following fixed issues that have a significant impact. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| :_newdoc-version: 2.18.5 | ||
| :_template-generated: 2026-02-09 | ||
| :_mod-docs-content-type: REFERENCE | ||
|
|
||
| [id="known-issues-8-1-0_{context}"] | ||
| = Known issues | ||
|
|
||
| [role="_abstract"] | ||
| {ProductFirstRef} ({ProductShortName}) version 8.1.0 is affected by the following newly identified and previously known issues. A known issue is listed in all future release notes until resolved, at which point it is published as a fixed issue. | ||
|
|
||
| //To be confirmed by SME (the comment is in the ticket) | ||
|
|
||
| //// | ||
| {ProductShortName} UI does not trigger rules for dependencies for Gradle applications:: | ||
| When you run a `source+dependency` analysis for a Gradle application by using the {ProductFullName} user interface (UI), the tool does not trigger rules for dependencies. As a consequence, the analysis does not trigger issues on open source libraries | ||
|
|
||
| Note that this known issue does not affect the {ProductShortName} command-line interface (CLI). | ||
|
|
||
| (link:https://issues.redhat.com/browse/MTA-6211[MTA-6211]) | ||
| //// | ||
|
|
||
|
|
| Original file line number | Diff line number | Diff line change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,75 @@ | ||||||||||||||
| :_newdoc-version: 2.18.5 | ||||||||||||||
| :_template-generated: 2026-02-13 | ||||||||||||||
| :_mod-docs-content-type: REFERENCE | ||||||||||||||
|
|
||||||||||||||
| [id="new-features-and-enhancements-8-1-0_{context}"] | ||||||||||||||
| = New features and enhancements | ||||||||||||||
|
|
||||||||||||||
| [role="_abstract"] | ||||||||||||||
| {ProductFirstRef} ({ProductShortName}) version 8.1.0 provides the following major new features and enhancements. | ||||||||||||||
|
|
||||||||||||||
|
|
||||||||||||||
| Centralized configuration management across components for standardizing analysis configuration and custom rules:: | ||||||||||||||
mpershina marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||||||||
| You can use the centralized configuration management to standardize analysis configurations and custom rules for the following {ProductFullName} components: | ||||||||||||||
|
|
||||||||||||||
| * User interface (UI) | ||||||||||||||
| * Command-line interface (CLI) | ||||||||||||||
| * The Visual Studio Code {ProductShortName} extension. | ||||||||||||||
|
|
||||||||||||||
| + | ||||||||||||||
| -- | ||||||||||||||
| Profiles contain analysis configuration that allows organizations to standardize configuration and simplify configuration management by adopting a platform engineering approach. The architect can create, update, and delete profiles and custom rules. Migrators can sync with the {ProductShortName} Hub to download available configuration bundles and use them to run an analysis in the UI, CLI, and by using the Visual Studio Code plugin. | ||||||||||||||
mpershina marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||||||||
|
|
||||||||||||||
| (link:https://issues.redhat.com/browse/MTA-6491[MTA-6491]) | ||||||||||||||
| -- | ||||||||||||||
|
|
||||||||||||||
|
|
||||||||||||||
| The {ProductShortName} Visual Studio Code extension pack and the Core extension with language-specific extension are available:: | ||||||||||||||
mpershina marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||
| The {ProductFullName} Visual Studio Code extension consists of an analyzer RPC binary that runs an analysis for the following applications: | ||||||||||||||
|
|
||||||||||||||
mpershina marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||
| * Java | ||||||||||||||
| * Go | ||||||||||||||
|
||||||||||||||
| * Go | |
| * Core extension | |
| * Java extension | |
| * C# extension | |
| * Javascript extension | |
| * Go extension |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Javascript is more accurate I think, it's not limited to nodejs applications
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure both C# and .NET extensions exist.
@savitharaghunathan @hhpatel14 could you please take a look?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it's just one extension. I'd probably just call it C#
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Then I shall remove .NET from the docs (we have a couple of mentions within the docset)
Pkylas007 marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| (Placeholder) Support for LLM Proxying with MTA | |
| {ProductShortName} supports proxy service to connect with the LLM | |
| You can opt to allow client endpoints, for example the {ProductShortName} Visual Studio Code extension, use the proxy service to access the large language models (LLMs). The client uses Keycloak credentials to authenticate to the {ProductShortName} Hub. To authenticate to the LLM, the client sends JSON Web Token (JWT) issued by Keycloak to the proxy service. The proxy service validates the client's JWT against the Hub's Keycloak instance. In a separate process, the proxy service authenticates to the LLM by using the cluster secret that contains the LLM API key configured by the administrator. Thus, the proxy service allows administrators to create, manage, and rotate LLM API keys while eliminating the need to share the LLM key with multiple client endpoints. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The llm-proxy is a service within the Konveyor APIs. Centralized config is what allows the syncing of analysis profiles etc, and when it is enabled and a proxy is deployed in the cluster, it will also set the IDE extension to use the proxy. But there is no proxy when connecting to the hub, the hub and the proxy are separate services inside the konveyor deployment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fabianvf I have modified the description. Can you please review?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fabianvf, a kind reminder to review the suggested text.
Thank you!
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| :_newdoc-version: 2.18.5 | ||
| :_template-generated: 2026-02-26 | ||
| :_mod-docs-content-type: REFERENCE | ||
|
|
||
| [id="tech-preview-8-1-0_{context}"] | ||
| = Technology Preview features | ||
|
|
||
| [role="_abstract"] | ||
| This section provides a list of all Technology Preview features available in {ProductFullName} ({ProductShortName}) 8.1.0. | ||
|
|
||
| For information on Red Hat's scope of support for Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope]. | ||
|
|
||
|
|
||
| C# provider for analyzing C# applications in `source-only` mode across {ProductShortName} components (Technology Preview):: | ||
mpershina marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| You can use the external `csharp` provider to run an analysis in `source-only` mode for C# source code in the {ProductFullName} command-line interface (CLI), user interface, and the {ProductShortName} Visual Studio Code extension. `csharp` parses the source code by using tree-sitter and uses stack graph for the analysis to find references to types, methods, classes, and fields. Based on the `C#` rule definition, the analyzer identifies violations in your code that you must resolve before the application migration. | ||
| + | ||
| (link:https://issues.redhat.com/browse/MTA-6492[MTA-6492]) | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also include in this doc that C# analysis support is now fully supported from the WebUI. It is dev preview but worth calling out