-
Notifications
You must be signed in to change notification settings - Fork 62
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
Relocate ActionMailbox #162
Conversation
@ssunday fyi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sqlite can be killed from the gemfiles/X, no?
@@ -1,3 +1,3 @@ | |||
options = {} | |||
ActionMailer::Base.add_delivery_method :ses, Aws::ActionMailer::SESMailer, **options | |||
ActionMailer::Base.add_delivery_method :ses_v2, Aws::ActionMailer::SESV2Mailer, **options | |||
ActionMailer::Base.add_delivery_method :ses, Aws::ActionMailer::SES::Mailer, **options |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this an unrelated to mailbox change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's in the sample-app. A change I made for the other gem. I just forgot to change it here, and when testing ActionMailbox, I got an unrelated error.
Yes. I can do this now. My original plan was to just do a sweeping clean up after I got all of the functionality out. |
@ssunday All approved from our side. I think you can actually test this if you pull in aws-sdk-rails from github/branch in your gemfile, this gem and the other gems the same way. It should all still work. Otherwise, we can defer that and if you want to give approves that's fine too. |
Relocates the ActionMailbox SES feature to aws/aws-actionmailbox-ses-ruby#1