terraform-converter

To create a Terraform converter for an AWS service, you generate a new converter module file, map Terraform resources to the project's state view, and register it within the winterbaume-terraform crate. This ensures schema validation and test coverage.

A Terraform converter maps AWS service resources to a stateful project view, enabling automatic coverage and integration with the Terraform state workflow. You need one when adding support for new AWS services or improving existing resource field coverage.

To improve field coverage on an existing Terraform AWS converter, you enhance the resource mapping logic to increase inject and extract accuracy. This achieves higher coverage scores when evaluated against the Terraform AWS provider schema.

Yes, the Terraform converter validates against the AWS provider schema. After registering the converter with the Terraform integration, you run schema coverage checks and validate the implementation through tests to ensure accuracy.

Yes, you can use the converter for stateful AWS services like S3 and EC2. The workflow guides you through creating a converter module for a chosen service, mapping its Terraform resources to the project's state view for integration.

The best way to integrate a new AWS service converter is to follow the project template to create or extend a module, register it with the Terraform integration, and run schema coverage checks. This ensures seamless state workflow integration.