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

Write and run management command to send email notifying registered API users of the new api.openverse.org domain #3742

Closed
sarayourfriend opened this issue Feb 2, 2024 · 1 comment
Assignees
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API

Comments

@sarayourfriend
Copy link
Contributor

sarayourfriend commented Feb 2, 2024

Description

Part of https://docs.openverse.org/projects/proposals/infrastructure_improvements/20240105_implementation_plan_move_remaining_services_to_openverse_org.html#move-the-django-api-to-api-openverse-org

Refer to this previous email-sending management command for an example of how we have managed this in the past. Record successfully sent email recipients in Redis, to ensure the command is idempotent.

Staff only because this will require composing the email body and then running the management command in production

Blocked by https://github.com/WordPress/openverse-infrastructure/issues/778

The email body should specify a date for when the openverse.engineering domains will start permanently redirecting to openverse.org domain. That date should be at least two weeks in the future from the date the email is sent.

Update https://github.com/WordPress/openverse-infrastructure/issues/783 with the decided date.

Ideally #3743 is completed around the same time and includes the decided transition date.

@sarayourfriend sarayourfriend added 🟨 priority: medium Not blocking but should be addressed soon 🌟 goal: addition Addition of new feature 💻 aspect: code Concerns the software code in the repository ⛔ status: blocked Blocked & therefore, not ready for work 🧱 stack: api Related to the Django API labels Feb 2, 2024
@sarayourfriend sarayourfriend self-assigned this Apr 30, 2024
@sarayourfriend sarayourfriend removed the ⛔ status: blocked Blocked & therefore, not ready for work label Apr 30, 2024
@sarayourfriend
Copy link
Contributor Author

The emails are sent as of 2024-05-08T00:59:58.366Z.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API
Projects
Archived in project
Development

No branches or pull requests

1 participant