Better handling when Cloudformation resources are converted to the wrong Terraform resource.
shadycuz opened this issue · comments
It's possible that a Cloudformation resource will get converted to the wrong terraform resource. Perhaps its because the resource is custom #186 . Maybe its just a bad match. We have the match percentage but often the correct match is a really low percentage.
Searcing for events rule in terraform docs...
Best match was cloudwatch event rule at /tmp/terraform_src/website/docs/r/cloudwatch_event_rule.html.markdown with score of 62.
The only think I can think of, is before every resource, write the Cloudformation logical ID and resource type that it was converted from.
Something like
// Converted from MyEventsRule (AWS::Events::Rule)
resource "aws_cloudwatch_event_rule" "my_events_rule" {
name = "foo"
}
That way, if the resource match is wrong, at least they can see about fixing it.