Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions best-practices.md
Original file line number Diff line number Diff line change
@@ -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. <br>
> 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.

Expand Down
4 changes: 0 additions & 4 deletions deploy/docs/main/mta-v7.x/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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. <br>
> 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.

Expand Down
4 changes: 0 additions & 4 deletions deploy/docs/main/mtv-migration/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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. <br>
> 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.
Expand Down
5 changes: 0 additions & 5 deletions deploy/docs/main/mtv-plan/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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. <br>
> Any reference to assessment workflows will be obsolete.

4 changes: 0 additions & 4 deletions workflows/azure/README.md
Original file line number Diff line number Diff line change
@@ -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. <br>
> 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.

Expand Down
4 changes: 0 additions & 4 deletions workflows/mta-v7.x/README.md
Original file line number Diff line number Diff line change
@@ -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. <br>
> This workflow, being an assessment workflow, will be obsolete and irrelevant.

# MTA - migration analysis workflow

# Synopsis
Expand Down
4 changes: 0 additions & 4 deletions workflows/mtv-migration/README.md
Original file line number Diff line number Diff line change
@@ -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. <br>
> 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)
Expand Down