feat(migrations): add file metadata to S3 files #3804
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
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.
Changes
This PR adds a migration for S3 files created using File Manager. The new asset delivery system needs to bootstrap the entire Webiny context, which requires information about tenant and locale. The only possible way to provide this information to the system is if we can resolve it based on a file key. For this purpose, we're creating an extra
.metadatafile with every file created via the File Manager.How Has This Been Tested?
Manually, by uploading 1000+ files in an older system, then upgrading to an unstable release, and running the migration. After the deployment, all files continue to work as expected.