Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataPusher integration issues #1446

Merged
merged 6 commits into from
Jan 24, 2014
Merged

Conversation

amercader
Copy link
Member

Mostly documentation and clean ups

@ghost ghost assigned joetsoi Jan 23, 2014
There's no need to prevent the import to the datastore on them, as the
datastore will manage the authorization, and logged in users still
expect these files to get imported to the DataStore.
@amercader
Copy link
Member Author

@kindly you may want to have a look at this instead of @joetsoi if you are testing datapusher. I've included the change to the datapusher notify method for allowing private datasets here

kindly added a commit that referenced this pull request Jan 24, 2014
@kindly kindly merged commit e8c8bda into master Jan 24, 2014
amercader added a commit that referenced this pull request Jan 24, 2014
amercader added a commit that referenced this pull request Jan 24, 2014
There's no need to prevent the import to the datastore on them, as the
datastore will manage the authorization, and logged in users still
expect these files to get imported to the DataStore.
@smotornyuk smotornyuk deleted the 1446-datapusher-integration-issues branch December 19, 2018 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants