Skip to content

Introduce logo placement API endpoint #1849

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

Merged
merged 11 commits into from
Aug 27, 2021
Merged

Introduce logo placement API endpoint #1849

merged 11 commits into from
Aug 27, 2021

Conversation

berinhard
Copy link
Contributor

This PR is complementary to #1806 work. It introduces a new endpoint /api/v2/sponsors/logo-placement/ to list all of the sponsor logo placement information. This endpoint replaces the previous gen_sponsors_csv management command we've created to start with the integrations with the logo placement server.

@ewdurbin, although this PR has all the code needed by the endpoint the CSV file still have invalid URLs for the logo images, such as https://pypi.org/static/images/sponsors/color/google.png. Feel free to update the CSV file with the new you'll generate after you go through the process of updating the uploaded files.

@berinhard berinhard requested a review from ewdurbin August 24, 2021 14:00
@berinhard berinhard force-pushed the logo-placement-endpoint branch from 4e11447 to b4ee966 Compare August 26, 2021 20:00
@berinhard berinhard requested a review from ewdurbin August 26, 2021 20:00
@berinhard
Copy link
Contributor Author

@ewdurbin this PR is ready for review. You can notice I added a missing migration with cb7ceb5. To make it easier to merged/deployed, I cherry-picked the commit on a separate branch and opened the PR #1851.

@ewdurbin ewdurbin merged commit 113dacd into main Aug 27, 2021
@ewdurbin ewdurbin deleted the logo-placement-endpoint branch August 27, 2021 12:12
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.

2 participants