You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Workflow spec.arguments.parameters should support an enumFrom argument that works in a similar manner to the valueFrom
Use Cases
We currently use workflows for CRUD operations involving ephemeral environments. "enum" is super helpful to provide developers with a list of options to select from. Our current workflows for upgrading and uninstalling applications within an env looks like:
Some developers can also create new environments using a create-environment workflow. In addition to other things the create-environment workflow modifies the workflow templates for uninstall-application and upgrade-application by adding the new destination to the list of enums. The destroy-environment workflow does the same, it modifies the workflow templates and removes a destination from the enum options.
It would be far easier if the workflow template could fetch the enum values from an external resource, similar to how the "value" can be fetched using valueFrom.configMapKeyRef.
Summary
Workflow
spec.arguments.parameters
should support anenumFrom
argument that works in a similar manner to thevalueFrom
Use Cases
We currently use workflows for CRUD operations involving ephemeral environments. "enum" is super helpful to provide developers with a list of options to select from. Our current workflows for upgrading and uninstalling applications within an env looks like:
Some developers can also create new environments using a
create-environment
workflow. In addition to other things thecreate-environment
workflow modifies the workflow templates foruninstall-application
andupgrade-application
by adding the new destination to the list of enums. Thedestroy-environment
workflow does the same, it modifies the workflow templates and removes a destination from the enum options.It would be far easier if the workflow template could fetch the enum values from an external resource, similar to how the "value" can be fetched using valueFrom.configMapKeyRef.
Proposed Syntax
The current way we do this is rather janky and prone to errors.
This feature could be useful when many workflows have to share some common elements from a single source of truth (the configmap)
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: