Description
Description
In order to take advantage of automation opportunities presented by the aws-sdk-go-v2, and to reduce the long term upgrade burden we will no longer accept net-new resources or data sources based on aws-sdk-go.
In a similar vein to take advantage of the improved developer experience of the terraform-plugin-framework we will no longer accept net-new resources or data sources based on terraform-plugin-sdk.
The date of this change will be dictated by the following being completed:
- All examples and guidance in contributor focused documentation should be focused on aws-sdk-go-v2 / terraform-plugin-framework. We should keep older examples in order to facilitate best practice for existing resources.
- Our templating tool (skaff) should default to using aws-sdk-go-v2 / terraform-plugin-framework skaff: default to plugin framework #33508
- A GitHub action or check to comment/perform check on any PR containing a new datasource/resource explaining that the use of aws-sdk-go-v2 / terraform-plugin-framework is required.
- Messaging to indicate that the priority of existing PRs based on aws-sdk-go/terraform-plugin-sdk is not affected by their use. While the maintainers appreciate the work to update them to aws-sdk-go-v2, we are happy to update them if they are not.
Maintainer update
As of 10/20/2023, this policy is in effect. Existing pull requests do not need to be re-written to use AWS SDK for Go V2 and Terraform Plugin Framework. Where applicable maintainers will assist in changing these libraries. Enhancements and bug fixes do not require updating existing resources to use preferred libraries. This change only applies to net-new resources and data sources.