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.
The basic idea here is pretty simple: RMI has indicated to us that metadata is fairly nonsensitive, while the contents of the data (portfolios and reports) is hugely sensitive. My approach to this is to centralize the creation of download URLs in a single place (kind of the opposite of what we did for ADSCI's blob population logic). Additionally, we don't want to populate these proactively because RMI wants audit logs when people actually access the objects. Thus, here's my approach (which this PR starts to implement):
fetch
andReadableStream
to increase the percentage done as the download (or downloads) complete.Thoughts?