Closed bflad closed 4 years ago
These upstream resources require sweepers added:
aws_budgets_budget
- https://github.com/terraform-providers/terraform-provider-aws/pull/13210aws_db_event_subscription
- https://github.com/terraform-providers/terraform-provider-aws/pull/13213aws_glacier_vault
- https://github.com/terraform-providers/terraform-provider-aws/pull/13184aws_iot_topic_rule
- https://github.com/terraform-providers/terraform-provider-aws/pull/13245aws_neptune_event_subscription
- https://github.com/terraform-providers/terraform-provider-aws/pull/13214aws_redshift_event_subscription
- https://github.com/terraform-providers/terraform-provider-aws/pull/13215aws_ses_configuration_set
- https://github.com/terraform-providers/terraform-provider-aws/pull/13216aws_ses_domain_identity
- https://github.com/terraform-providers/terraform-provider-aws/pull/13217aws_ses_email_identity
- https://github.com/terraform-providers/terraform-provider-aws/pull/13217aws_ses_receipt_rule_set
- https://github.com/terraform-providers/terraform-provider-aws/pull/13169aws_sns_platform_application
- https://github.com/terraform-providers/terraform-provider-aws/pull/13168Also aws_backup_vault_notifications
added via https://github.com/terraform-providers/terraform-provider-aws/pull/12501.
As a follow on, use the new internal waiters
package added for aws_db_event_subscription
etc. in the main resource code.
This has been released in version 2.62.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 for triage. Thanks!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!
Community Note
Description
The acceptance testing can leave lingering resources on failed runs (e.g. via coding issues during development or panics). These lingering resources can cause quota limits to be reached, extraneous money to be spent, or in some worst cases leave open security risks in the testing account.
We do not require sweeper implementation during initial resource implementation at this time, but this may change in the future when the process can be simplified and documented better.
e.g. after many years of daily (or more) testing runs
This resource sweeper should have dependencies on upstream resources, e.g. (some sweepers may not be implemented)
New or Affected Resource(s)
Definition of Done