feat New Workflows Input Parameters

[LucasGrimauth]

Context

Related Issues(s): ISEEC-2514

Build Number: 3.4.22

Checklist:

• Verified in an integrated environment
• Unit and integration tests passing
• Semantic HTML with accessibility support
• No linting, test console, or browser console errors (best effort)
• JSDoc comment blocks for complex code

PR Review Guidance

Added Creatable, Creatable Pair, Date, Date Range and Multi Select parameters to workflows.

[tlawrie]

Thanks @LucasGrimauth. We need to map this to a GitHub issue in Roadmap as well.

The bigger part though that I think we need to go through is how these input types will be stored and handle by the Workflow Service, Controller Service, and Tasks. Any changes to Parameters can have an impact throughout the entire stack for Flow.

This analysis will need to be done prior to it being merged into the front-end.

[BenjaminRuby]

Hey @tlawrie could you connect with @marcusdroy on your concerns here? This is something that we were hoping to add as part of our next core release to align the parameters in flow with what is available in core

[tlawrie]

Hi @BenjaminRuby sure this can be discussed at the next community meeting.

We will also need a github issue attached to 3.5.1. or 3.6.0

In terms of the technical discussion considering this is an IBM proposal, id suggest that the relevant technical details on both the front end and back end have to align and all of the information be in the GitHub issue. This means that if a Parameter type is introduced or changed on the front end, it has to be handled by the backend AND be able to be handled by Tekton. Which in this case, I'm not aware of any discussion or analysis being performed about how those would be passed through and understood by Tekton.