Add support for listing nested tracks #1319
Merged
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
DJRickyB
added
enhancement
DJRickyB
changed the title
ebadyano
approved these changes
Aug 31, 2021
DJRickyB
pushed a commit
that referenced
this pull request
Sep 2, 2021
DJRickyB
added a commit
that referenced
this pull request
Sep 22, 2021
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.
with this commit we add support for listing nested tracks in git-based track repositories. Previously,
esrally list trackswould only list top-level directories in a target track repo which contained atrack.json. This change causes full recursive search in the track repository, to better support the idea of "nested" track structures.Fixes #1086