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

Add some sort of webhooks support #360

Open
ralphbean opened this issue Feb 19, 2015 · 6 comments
Open

Add some sort of webhooks support #360

ralphbean opened this issue Feb 19, 2015 · 6 comments

Comments

@ralphbean
Copy link

(This is also for things like https://release-monitoring.org that want to find out about new releases of packages like in #347.)

Do you have any interest in having some sort of 'webhooks' support like github does? Something where release-monitoring.org admins (or admins of other sites) could login to warehouse and request that the warehouse app do an http POST back to them when new releases are uploaded?

With this, we could reduce load on your servers by never having to query again, plus we'd be notified of releases in near real-time (instead of waiting 12 hours for our cronjob to run again).

@TomasTomecek
Copy link

Other solution could be to do a real-time stream of releases with Transfer-Encoding: chunked.

@nlhkabu nlhkabu added the requires triaging maintainers need to do initial inspection of issue label Jul 2, 2016
@jakirkham
Copy link

Would this be per package? If so, that would be really interesting.

@di di removed the requires triaging maintainers need to do initial inspection of issue label Dec 7, 2017
@brainwane brainwane added this to the 6. Post Legacy Shutdown milestone Feb 12, 2018
@brainwane
Copy link
Contributor

Thanks for the suggestion and discussion, @ralphbean and @TomasTomecek and @jakirkham, and sorry for the slow response!

The folks working on Warehouse have gotten funding to concentrate on improving and deploying Warehouse, and have kicked off work towards our development roadmap -- the most urgent task is to improve Warehouse to the point where we can redirect pypi.python.org to pypi.org so the site is more sustainable and reliable.

In our meeting today we discussed this issue. Since this feature isn't something that the legacy site has, we decided this belongs in a future milestone, and so I've moved it.

As Dustin mentioned in #2413, we do currently have https://pypi.org/rss/packages.xml -- I know this isn't as awesome as having webhooks would be, but at least it's something. I've also just created an issue label for API- and feed-related bugs and feature requests, and added this to it, to make it easier for the maintainers to see the ways package maintainers and other Python developers want to interact with Warehouse programmatically.

Thanks and sorry again for the wait.

@jakirkham
Copy link

Thanks for the update. No worries.

...the most urgent task is to improve Warehouse to the point where we can redirect pypi.python.org to pypi.org so the site is more sustainable and reliable.

Completely agree! Would be great to see pypi.org become stable. Thanks for working on it. :)

@brainwane
Copy link
Contributor

Carrying over a reminder from #2413: when we implement webhooks support, we should document it in https://warehouse.readthedocs.io/security/#project-and-release-activity-details and https://test.pypi.org/help/#APIs .

@brainwane
Copy link
Contributor

I'll also mention that API-related issues are things we could work on at the PyCon sprints in May.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants