Option to maintain local cache file in Remote #428
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
PikachuEXE
reviewed
Aug 26, 2022
PikachuEXE
approved these changes
Aug 26, 2022
|
Released in |
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.
With
remote_file_list_cache_file_pathoptions we could be able to reduce and sync time by 30 minutes.Maintaining the local file is difficult in the docker environment, so in this PR providing the option to have the cache file in remote (
remote_file_list_remote_path) as well. Which will be downloaded during asset sync if path is configured and its creates a local file for further references in the sync. Once after the sync is completed, updated local cache file will be uploaded back to configured remote path.This remote cache file will be maintained in the path configured using
remote_file_list_remote_pathinsidefog_directory