Open
Conversation
* adding boto3 to requirements for library to push data to s3 * moving query functionality to Account class in npsp * moving _push_to_s3 function to util * adding celery task that can be triggered nightly to push to s3
adding in donor wall query pieces from tt app
Add route for donor wall, pull in static header content
…days worth of data. Currently have debug data output for created day for each donation record
mostly a stop-gap until we have new SF fields
from query
updated copy
yes indeed
was missing before
and center remaining options
Update/blast price 26
for elections 26
This file contains hidden or 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
3 participants
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.
What's this PR do?
Why are we doing this? How does it help us?
How should this be manually tested?
How should this change be communicated to end users?
Are there any smells or added technical debt to note?
What are the relevant tickets?
Have you done the following, if applicable:
(optional: add explanation between parentheses)
TODOs / next steps: