Add import of aws_ses_active_receipt_rule_set resource

[yktakaha4]

Enable Import with the following command.

terraform import aws_ses_active_receipt_rule_set.my_rule_set my_rule_set_name

As a specification of SES, only one active receipt rule set is valid within the same region.

describe-active-receipt-rule-set AWS API cannot take any arguments and return an active rule set when called.
Import command will succeed only if the rule_set_name passed matches the API return value.

ref: https://docs.aws.amazon.com/cli/latest/reference/ses/describe-active-receipt-rule-set.html

Relations

Closes #29369

References

If no Active ruleset exists, Import will fail.

$ terraform import aws_ses_active_receipt_rule_set.my_rule_set hoge
aws_ses_active_receipt_rule_set.my_rule_set: Importing from ID "hoge"...
╷
│ Error: no active Receipt Rule Set found
│ 
│ 
╵

Import will also fail if the ruleset names do not match.

$ terraform import aws_ses_active_receipt_rule_set.my_rule_set fuga
aws_ses_active_receipt_rule_set.my_rule_set: Importing from ID "fuga"...
╷
│ Error: SES Receipt Rule Set (fuga) belonging to SES Active Receipt Rule Set not found
│ 
│ 
╵

If rule_set_name matches,

$ terraform import aws_ses_active_receipt_rule_set.my_rule_set hoge
aws_ses_active_receipt_rule_set.my_rule_set: Importing from ID "hoge"...
aws_ses_active_receipt_rule_set.my_rule_set: Import prepared!
  Prepared aws_ses_active_receipt_rule_set for import
aws_ses_active_receipt_rule_set.my_rule_set: Refreshing state... [id=hoge]

Import successful!

The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.

$ terraform plan                                                   
╷
│ Warning: Provider development overrides are in effect
│ 
│ The following provider development overrides are set in the CLI configuration:
│  - hashicorp/aws in /home/tkhs/go/bin
│ 
│ The behavior may therefore not match any released version of the provider and applying changes may cause the state to become incompatible with published releases.
╵
aws_ses_active_receipt_rule_set.my_rule_set: Refreshing state... [id=hoge]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.

Output from Acceptance Testing

In my local.

$ make testacc TESTS=TestAccSESActiveReceiptRuleSet PKG=ses       
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/ses/... -v -count 1 -parallel 20 -run='TestAccSESActiveReceiptRuleSet'  -timeout 180m
=== RUN   TestAccSESActiveReceiptRuleSet_serial
=== RUN   TestAccSESActiveReceiptRuleSet_serial/DataSource
=== RUN   TestAccSESActiveReceiptRuleSet_serial/DataSource/basic
=== RUN   TestAccSESActiveReceiptRuleSet_serial/DataSource/noActiveRuleSet
=== RUN   TestAccSESActiveReceiptRuleSet_serial/Resource
=== RUN   TestAccSESActiveReceiptRuleSet_serial/Resource/basic
=== RUN   TestAccSESActiveReceiptRuleSet_serial/Resource/disappears
--- PASS: TestAccSESActiveReceiptRuleSet_serial (98.90s)
    --- PASS: TestAccSESActiveReceiptRuleSet_serial/DataSource (38.36s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/DataSource/basic (33.18s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/DataSource/noActiveRuleSet (5.17s)
    --- PASS: TestAccSESActiveReceiptRuleSet_serial/Resource (60.54s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/Resource/basic (32.96s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/Resource/disappears (27.58s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/ses        98.980s

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[kamilturek]

LGTM 👍

[yktakaha4]

@kamilturek @ewbankkit Is there anything I can do to help with this PR merge?
I look forward to using this PR in production code.

[yktakaha4]

Conflicts resolved.

$ make testacc TESTS=TestAccSESActiveReceiptRuleSet PKG=ses
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/ses/... -v -count 1 -parallel 20 -run='TestAccSESActiveReceiptRuleSet'  -timeout 180m
=== RUN   TestAccSESActiveReceiptRuleSet_serial
=== PAUSE TestAccSESActiveReceiptRuleSet_serial
=== CONT  TestAccSESActiveReceiptRuleSet_serial
=== RUN   TestAccSESActiveReceiptRuleSet_serial/Resource
=== RUN   TestAccSESActiveReceiptRuleSet_serial/Resource/basic
=== RUN   TestAccSESActiveReceiptRuleSet_serial/Resource/disappears
=== RUN   TestAccSESActiveReceiptRuleSet_serial/DataSource
=== RUN   TestAccSESActiveReceiptRuleSet_serial/DataSource/basic
=== RUN   TestAccSESActiveReceiptRuleSet_serial/DataSource/noActiveRuleSet
--- PASS: TestAccSESActiveReceiptRuleSet_serial (86.02s)
    --- PASS: TestAccSESActiveReceiptRuleSet_serial/Resource (55.87s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/Resource/basic (31.21s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/Resource/disappears (24.66s)
    --- PASS: TestAccSESActiveReceiptRuleSet_serial/DataSource (30.15s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/DataSource/basic (25.59s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/DataSource/noActiveRuleSet (4.56s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/ses        86.129s

[jar-b]

LGTM 🎉

$ make testacc PKG=ses TESTS=TestAccSESActiveReceiptRuleSet_serial
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/ses/... -v -count 1 -parallel 20 -run='TestAccSESActiveReceiptRuleSet_serial'  -timeout 180m
=== RUN   TestAccSESActiveReceiptRuleSet_serial
=== PAUSE TestAccSESActiveReceiptRuleSet_serial
=== CONT  TestAccSESActiveReceiptRuleSet_serial
=== RUN   TestAccSESActiveReceiptRuleSet_serial/Resource
=== RUN   TestAccSESActiveReceiptRuleSet_serial/Resource/basic
=== RUN   TestAccSESActiveReceiptRuleSet_serial/Resource/disappears
=== RUN   TestAccSESActiveReceiptRuleSet_serial/DataSource
=== RUN   TestAccSESActiveReceiptRuleSet_serial/DataSource/basic
=== RUN   TestAccSESActiveReceiptRuleSet_serial/DataSource/noActiveRuleSet
--- PASS: TestAccSESActiveReceiptRuleSet_serial (50.98s)
    --- PASS: TestAccSESActiveReceiptRuleSet_serial/Resource (32.66s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/Resource/basic (18.04s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/Resource/disappears (14.62s)
    --- PASS: TestAccSESActiveReceiptRuleSet_serial/DataSource (18.32s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/DataSource/basic (15.94s)
        --- PASS: TestAccSESActiveReceiptRuleSet_serial/DataSource/noActiveRuleSet (2.37s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/ses        54.441s

[jar-b]

Thanks for your contribution, @yktakaha4! 👍

[github-actions]

This functionality has been released in v5.5.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.