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

Added /emails/:id/retry/ endpoint for retrying failed emails #11410

Merged
merged 1 commit into from
Nov 22, 2019

Conversation

kevinansfield
Copy link
Contributor

@kevinansfield kevinansfield commented Nov 21, 2019

We want to allow admin users to trigger a retry of failed emails without having to go through the unpublish/republish dance.

  • fixed resource identifier in email permissions migration so email permissions are added correctly
  • added new email permissions migration so that beta releases can be upgraded without rollback (will be a no-op for any non-beta upgrades)
  • added /emails/:id/retry/ canary Admin API endpoint
    • follows same URL pattern as theme activation
    • only triggers mega service retry endpoint if the email has a 'failed' status
  • fixed email error translation keys

We want to allow admin users to trigger a retry of failed emails without having to go through the unpublish/republish dance.

- fixed resource identifier in email permissions migration so email permissions are added correctly
- added new email permissions migration so that beta releases can be upgraded without rollback (will be a no-op for any non-beta upgrades)
- added `/emails/:id/retry/` canary Admin API endpoint
  - follows same URL pattern as theme activation
  - only triggers mega service retry endpoint if the email has a `'failed'` status
@kevinansfield kevinansfield marked this pull request as ready for review November 22, 2019 13:54
@kevinansfield kevinansfield merged commit 6a057fa into TryGhost:mega Nov 22, 2019
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

2 participants