Draft: s3invsync setup -- inject AWS credentials for script for LINC #13
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
aaronkanzer
changed the title
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.
@kabilar -- extending some of the work you have in #11 already
Trying to build out more robust logging and proper authentication for Engaging
Cc @satra -- just tagging for visibility -- one of the challenges we might need to figure out is the time constraints of Engaging vs. how long the
s3invsyncscript takes -- going to do some stress testing (Engaging has a max of 12 hrs per job running), but wondering if I might end up chatting with John and Yarik about some sort of "checkpointing".Much more code to come -- will continue to update this script through today, tomorrow, early next week -- hoping we have a routine, authenticated cronjob-like script running soon for LINC