Open Pacerino opened 3 weeks ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @Pacerino 👋 Thank you for taking the time to raise this! It looks like this falls under its own service in the AWS Go SDK, so it would wind up being a separate service in the AWS Provider as well (as in, the resources would be named something like aws_mailmanager_*
. I've updated a couple of things about this issue with that in mind. There's no further action needed from you at this point, I just like to give people a heads up when I make those kinds of changes 🙂
Adding a different perspective, the AWS CC Provider already has the resources and they are named awscc_ses_mail_manager_*
, for example awscc_ses_mail_manager_relay
. So I wonder if there is any merit following suit for the new resources to be created in the AWS Provider.
Description
AWS SES has recently added a new function that allows you to manage incoming mails for SES or create rules and routes. This function is called “Mail Manager” and is mapped directly in SES, so it is not a separate new service. Right now without this
Requested Resource(s) and/or Data Source(s)
aws_ses_relay aws_ses_archive aws_ses_ingress aws_ses_traffic_policy
Potential Terraform Configuration
No response
References
https://github.com/aws/aws-sdk-go-v2/tree/main/service/mailmanager https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/mailmanager https://docs.aws.amazon.com/ses/latest/dg/eb.html
Would you like to implement a fix?
No