Remove cross-references too specific to TR registry examples

[ezgidemirel]

What problem are you facing?

We started to inject cross-references based on the examples coming from Terraform registry. Sometimes, these references may support multiple types or sometimes do not refer to the leaf reference. For example, target_host_name, might be a Linux VM or a Microsoft VM. Another example might be network_interface_id in here. There exists a separate resource type called network_interface but due to this example, we're referring to an EC2 instance to get the value.

Therefore we need to be careful about what we inject while configuring the resources and delete the ones which may not make sense like here.

How could Terrajet help solve your problem?

Unfortunately, there is no straightforward solution to this problem. One thing we may implement is traversing references to reach out to the leaf one and use its type in the resolver.