Contributors spend a significant amount of their time manually writing flatteners and expander functions to map AWS SDK for Go types to Terraform sdk/framework types and vice-versa. This could be generated from AWS SDK types and potentially added to skaff. This would allow the majority of this work to be generated and reduce errors in this data handling.
Ideally this could be done at any time, so updates to AWS SDK types could be handled by refreshing generation for the types used in each resource.
This would significantly reduce writing boilerplate code, improving productivity for contributors as well as reducing the onus on review time for maintainers.
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.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Description
Contributors spend a significant amount of their time manually writing flatteners and expander functions to map AWS SDK for Go types to Terraform sdk/framework types and vice-versa. This could be generated from AWS SDK types and potentially added to skaff. This would allow the majority of this work to be generated and reduce errors in this data handling.
Ideally this could be done at any time, so updates to AWS SDK types could be handled by refreshing generation for the types used in each resource.
This would significantly reduce writing boilerplate code, improving productivity for contributors as well as reducing the onus on review time for maintainers.
References