Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-2203

Reuse Scaffolder extensions in Orchestrator

XMLWordPrintable

    • Assimilate Scaffolder form extension mechanism into Orchestrator
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      This is a follow-up for FLPATH-1359, specifically for FLPATH-1360 .

       

      We need review the option of reusing the same mechanism for extending the RJSF forms as the Backstage Scaffolder does: https://backstage.io/docs/features/software-templates/writing-custom-field-extensions

       

      We might "copy" their mechanism to the Orchestrator, so the learning curve for customers will become shallow.
      Or we might reuse the exposed extensions (products of createScaffolderFieldExtension() ) and so make the development for both the Orchestrator and Templates transparent while keeping feature parity between those two which will be a benefit especially for the Workflow as Templates flow.

              Unassigned Unassigned
              mlibra@redhat.com Marek Libra
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: