[8.x] Allow multiple SES configuration with IAM Role authentication #37523
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Marco Deleu <deleugyn@gmail.com>
alustau
changed the title
deleugpn
approved these changes
May 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When trying to use multiple mailers with
sesas the transport, Laravel is trying to rely on the secret key to decide whether to use a local configuration (within mailers) or a global configuration (at services.ses). However, IAM Role-based authentication (assume role) doesn't require any key or secret to be present, which makes Laravel fallback to the global configuration and the mailer loses all 'local' configuration.This pull request will broaden the usage of specific mailer configuration, but still allow fallback to global configuration through the array_merge execution preference