Desired state is to get Flow Parameters aligned with what we are using in our IBM core platform.
Previously we had not created any parameter types in flow that could have multiple values. This was due to technical constraints around handling arrays. The proposed fix that has already been implemented from the front end (https://github.com/boomerang-io/flow.client.web/pull/105) is to use a comma separated string to store parameters that could have more than one value.
A summary of the paramter types that have been added as part of the above PR:
Creatable
Creatable Pair
Date
Date Range
Multi Select
Timeline
What's the timeline for this Epic, what resources are needed, and what might potentially block this from hitting the projected end date.
Open Questions
@marcusdroy and @tlawrie to discuss any potential issues with how Tekton might handle this proposed format.
Description
Desired state is to get Flow Parameters aligned with what we are using in our IBM core platform.
Previously we had not created any parameter types in flow that could have multiple values. This was due to technical constraints around handling arrays. The proposed fix that has already been implemented from the front end (https://github.com/boomerang-io/flow.client.web/pull/105) is to use a comma separated string to store parameters that could have more than one value.
A summary of the paramter types that have been added as part of the above PR:
Timeline
What's the timeline for this Epic, what resources are needed, and what might potentially block this from hitting the projected end date.
Open Questions
@marcusdroy and @tlawrie to discuss any potential issues with how Tekton might handle this proposed format.