Keeping with the theme of integrating more deeply with backstage, we propose a workflow

view under a specific component. Just like tekton pipeline runs, users could see the last runs of workflows which is specific to this component, and run new one if need to.

Using a component as a starting point for workflow execution gives all the context needed and that has several advantages:

• the component has a git repo - we can pass it to workflows that need those repo as input seemless ly
• component has maintainer group - we can pass that the the workflow to use notification, seemlessly
• gived the first points we can invoke some workflows without any form interaction - just one click to invoke
• project stakeholder get important notification from related workflows (migration faild/succeeded , new cluster created for the project, and so on)

Without the context of a component the workflow invoker needs to work too many details out - who to notify, what exact git repo to use (then copy paste) , and so on.

User Story:

As a component user I want to run an MTA modernization workflow from my componenet page, to analyze the state my component containerization readiness.
As a component user I want to see the latest workflows runs on my component

As a component maintainer I want to allow/block other users from running workflows on my component
As a project maintainer that has various component under me I want the project maintainers to be able to run MTA workflows easily

Backstage and entities setup:
See the tekton page as an example - they set annotation in the catalog yaml to inject the ui parts.
https://janus-idp.io/plugins/tekton/

An example mock for this (taken from one of our design docs  https://docs.google.com/document/d/13SGaeVRTxjQ1ulV3dEMcv27wivUSLCt8ZPBrFVztxwU