Add direct Atlos integration #137
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
milesmcc
force-pushed
the
milesmcc/atlos-integration
branch
from
9828dd4
to
532ed8a
Compare
msramalho
approved these changes
Apr 15, 2024
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.
This pull request adds a direct integration between Atlos (using some very new yet-undocumented API endpoints that are only available on our staging instance) and the auto archiver.
TODO:
processingin the feeder@msramalho, if you have time it would be very helpful if you could just take a quick look at this PR and let me know if you see any blaring issues/architectural decisions you'd change.
I did have to make some small changes to the way that storages access metadata, as it's necessary for us to have the metadata in order to know where to store each piece of media.