From 7f2a9e55d716f7ba4d8f6643305af5e881495232 Mon Sep 17 00:00:00 2001 From: Yaron Dayagi Date: Tue, 22 Jul 2025 17:58:27 +0300 Subject: [PATCH] remove assessment deprecation notice FLPATH-2323 https://issues.redhat.com/browse/FLPATH-2323 Signed-off-by: Yaron Dayagi --- best-practices.md | 4 ---- deploy/docs/main/mta-v7.x/README.md | 4 ---- deploy/docs/main/mtv-migration/README.md | 4 ---- deploy/docs/main/mtv-plan/README.md | 5 ----- workflows/azure/README.md | 4 ---- workflows/mta-v7.x/README.md | 4 ---- workflows/mtv-migration/README.md | 4 ---- 7 files changed, 29 deletions(-) diff --git a/best-practices.md b/best-practices.md index c0234a76..822addd0 100644 --- a/best-practices.md +++ b/best-practices.md @@ -1,7 +1,3 @@ -> **🚨 Deprecation Notice: 🚨** -> From Orchestrator release version 1.7, Workflow Types will be retired. All workflows will act as infrastructure workflows, and no workflow will act as an assesment workflow.
-> Any reference to assessment workflows in this document will be obsolete. - # Best practices when creating a workflow A workflow should be developed in accordance with the guidelines outlined in the [Serverless Workflow definitions][1] documentation. diff --git a/deploy/docs/main/mta-v7.x/README.md b/deploy/docs/main/mta-v7.x/README.md index 32f55ad3..d9d13e10 100644 --- a/deploy/docs/main/mta-v7.x/README.md +++ b/deploy/docs/main/mta-v7.x/README.md @@ -4,10 +4,6 @@ Mta A Helm chart for MTA serverless workflow -> **🚨 Deprecation Notice: 🚨** -> From Orchestrator release version 1.7, Workflow Types will be retired. All workflows will act as infrastructure workflows, and no workflow will act as an assesment workflow.
-> Any reference to assessment workflows will be obsolete. - Migration Toolkit for Application Analysis (MTA) v7.x workflow evaluates applications to determine potential risks and the associated costs of containerizing the applications. It uses the [MTA v7.x Operator](https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.0/html/introduction_to_the_migration_toolkit_for_applications/index) to perform the analysis. At the end of a successful assessment workflow, a link to the report will be available in Backstage, under the notifications plugin. diff --git a/deploy/docs/main/mtv-migration/README.md b/deploy/docs/main/mtv-migration/README.md index f142f76a..d22ee5ce 100644 --- a/deploy/docs/main/mtv-migration/README.md +++ b/deploy/docs/main/mtv-migration/README.md @@ -4,10 +4,6 @@ MTV Migration A Helm chart for the MTV Migration serverless workflow -> **🚨 Deprecation Notice: 🚨** -> From Orchestrator release version 1.7, Workflow Types will be retired. All workflows will act as infrastructure workflows, and no workflow will act as an assesment workflow.
-> Any reference to assessment workflows will be obsolete. - # Helm chart Configuration The following table lists the configurable parameters of the MTV Migration chart and their default values. diff --git a/deploy/docs/main/mtv-plan/README.md b/deploy/docs/main/mtv-plan/README.md index 5736b1dd..62ccbca3 100644 --- a/deploy/docs/main/mtv-plan/README.md +++ b/deploy/docs/main/mtv-plan/README.md @@ -3,8 +3,3 @@ MTV Plan =========== This workflow is deprecated. Please use [MTV Migration workflow](https://github.com/rhdhorchestrator/serverless-workflows/blob/main/deploy/docs/main/mtv-migration) - -> **🚨 Deprecation Notice: 🚨** -> From Orchestrator release version 1.7, Workflow Types will be retired. All workflows will act as infrastructure workflows, and no workflow will act as an assesment workflow.
-> Any reference to assessment workflows will be obsolete. - diff --git a/workflows/azure/README.md b/workflows/azure/README.md index 17ae5388..8f9c4480 100644 --- a/workflows/azure/README.md +++ b/workflows/azure/README.md @@ -1,7 +1,3 @@ -> **🚨 Deprecation Notice: 🚨** -> From Orchestrator release version 1.7, Workflow Types will be retired. All workflows will act as infrastructure workflows, and no workflow will act as an assesment workflow.
-> This workflow is a continuation of an assessment workflow. Therfore, that workflow will be obsolete and won't server as a perliminary to this one. See [examples](#how-to-run). - # Azure list subscriptions workflow The workflow logs in to Azure and lists the subscriptions. It uses token propagation. Therefore, it is meant to be used via RHDH UI and not via API. diff --git a/workflows/mta-v7.x/README.md b/workflows/mta-v7.x/README.md index 1256ab7b..ba1fceb4 100644 --- a/workflows/mta-v7.x/README.md +++ b/workflows/mta-v7.x/README.md @@ -1,7 +1,3 @@ -> **🚨 Deprecation Notice: 🚨** -> From Orchestrator release version 1.7, Workflow Types will be retired. All workflows will act as infrastructure workflows, and no workflow will act as an assesment workflow.
-> This workflow, being an assessment workflow, will be obsolete and irrelevant. - # MTA - migration analysis workflow # Synopsis diff --git a/workflows/mtv-migration/README.md b/workflows/mtv-migration/README.md index ef2e5be5..4cd0eae0 100644 --- a/workflows/mtv-migration/README.md +++ b/workflows/mtv-migration/README.md @@ -1,7 +1,3 @@ -> **🚨 Deprecation Notice: 🚨** -> From Orchestrator release version 1.7, Workflow Types will be retired. All workflows will act as infrastructure workflows, and no workflow will act as an assesment workflow.
-> This workflow is a continuation of an assessment workflow. Therfore, that workflow will be obsolete and won't server as a perliminary to this one. See [examples](#how-to-run). - # MTV migration workflow - MTV Migration execution workflow This workflow creates an MTV Plan and an MTV Migration. It waits for the final condition of each resource. Final condition is either success or failure. It is important to note that we rely on MTV to reach a final state. We do not impose our own timeout. [MTV Migration Plan documentation](https://docs.redhat.com/en/documentation/migration_toolkit_for_virtualization/2.6/html/installing_and_using_the_migration_toolkit_for_virtualization/migrating-vms-web-console_mtv#creating-migration-plans-ui)