Add array input handling #26
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replicated non-array behavior on non-NFS backends
It already does implicitly; If an expression evaluates to an array, that will be handled. Adding the arrays: option was just confusing
julianhess
reviewed
Feb 10, 2020
agraubert
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Users can now specify arbitrarily nested arrays as inputs, and use the adapter
arraysoption to pin the array as an input, instead of splitting it as multiple inputs. A 1-d pinned array will be passed as a bash array to all jobs. Pinned arrays of 2 or more dimensions will function like a regular job input, with one element of the outermost array being passed to each job (nested arrays are flattened)