Chapter 1. Migration toolkit for applications 8.2

When you deploy exported manifests with the kubectl apply command, existing resources in the target namespace are silently overwritten. This is standard kubectl apply behavior and not specific to the mta-ops command-line interface (CLI). As a consequence, you might accidentally overwrite existing workloads on the target cluster.

To work around this problem, manually verify that the target namespace does not have conflicting resources before deployment.

MTA-7103

The mta-ops transform command does not currently support the --overwrite flag. If a custom stage directory already exists, the pipeline stops. As a consequence, you cannot automatically overwrite existing custom modifications during a pipeline re-run.

To work around this problem, manually delete the existing transform or custom stage directory before you re-run the mta-ops transform command.

MTA-7234

After authenticating to the MTA web console as a Keycloak administrator, you cannot perform user management tasks because these tasks require new scopes for the user, role, and tokens resources in MTA. A local user with admin role can create and manage users.

To work around this problem, add the following scopes for administrator users in Keycloak:

After you configure an external identity provider (IdP) for authentication, MTA does not automatically redirect to the IdP login page. As a consequence, you must click the Sign in with <identity_provider> option on the MTA login page to access the IdP login page.

To work around this problem, set the idp_primary field to true in the Tackle custom resource (CR). The MTA Hub identifies the external IdP as the primary authentication method and automatically routes to its login page for authentication.

MTA-7236

When you use a wildcard to import packages used by an annotation in your Java source code, an MTA analysis does not trigger a violation for such annotations. As a consequence, you are unable to fix all occurrences of an annotation defined in a rule because MTA triggered no incidents for some annotations.

No known workaround exists.

MTA-6530

The MTA web console completes tech discovery and analysis of certain projects with errors. As a consequence, the tech discovery does not generate all relevant tags and the analysis could miss triggering issues.

To work around this problem, ensure that you have a Gradle or a Maven build file at the root directory of your project.

MTA-6140

When you run an analysis by using a custom YAML rule for a compiled Java binary in the MTA web console, MTA does not trigger a violation.

No known workaround exists.

MTA-5199

Before this update, MTA did not generate an analysis log when you used the --http-proxy or --https-proxy option in an MTA CLI analysis. As a consequence, you could not verify if MTA routed the analysis through the proxy. With this fix, you can verify proxy use because MTA analysis records the use of a proxy.

MTA-6553

Before this update, after you enabled the option to Consume insecure artifact repositories in the MTA web console, MTA discovery for Maven applications that use self-signed certificates failed. As a consequence, you could not generate deployment assets for the affected applications. With this fix, MTA connects with Maven application repositories that use a self-signed certificate and completes application discovery.

MTA-7361

Before this update, the MTA web console did not validate the custom YAML rules you upload for an analysis or in custom targets. As a consequence, if a rule contained invalid keys or syntax errors, you did not see an error message. With this fix, MTA improves user experience by validating the custom rules you upload in the web console.

MTA-6834

Before this update, MTA did not trigger violations for open source dependency libraries when analyzing Gradle applications. As a consequence, a source+dependency analysis generated fewer incidents in the static report. With this fix, MTA includes violations on open source dependencies in the Gradle analysis results.

MTA-6211