Fix assignment of sensitive git-annex metadata data via glob patterns (regression introduced by #739) #793
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.
I introduced a regression in #739, and it was not flagged by the tests.
This PR fixes the glob pattern to properly flag the files as sensitive.
This is critical as if any data management pipeline rely on heudiconv setting this metadata, then sensitive data might not be handled appropriately/exposed.
I added that feature to the regression test, as this already require datalad to download data.
@yarikoptic let me know if you prefer this test to be it in a separate function.