Minimum change to reflect new bucket locations #18
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.
See #12 for context (changes to the layout of the object store).
intake
metadata and catalog (just a file listing) have moved into the image buckets alongside thecyto_app
metadata.env
This is a small and quite blunt change - i think any more work on making it generic should defer until
cyto_app
so that the spatio-temporal metadata that is available with the sources is preserved along with the individual imagesTo test
The tests for new bucket locations will skip unless you have
ENDPOINT
and the JASMIN access tokens set in.env
(they should skip in the pipeline but that's ok imo, just doing a slow file listing)@Kzra